GREG 4.1.1 - customizing oracle - wso2

I have problem customizing $GREG_HOME/repository/conf/registry.xml file for oracle database 10, I am using ojdbc14_1.0.0.jar.
After recommendations at http://wso2.org/project/registry/4.1.1/docs/installation_guide/db_oracle.html
Edit $GREG_HOME/repository/conf/registry.xml and give the following:
oracle-db
jdbc:oracle:thin:#SERVER_NAME:PORT/DB_NAME
USER_NAME
PASSWORD
oracle.jdbc.driver.OracleDriver
80
60000
5
I have errors at the startup of carbon server ("function is not supported" in Russian):
" TID: [] [WSO2 Governance Registry] [2012-03-29 15:41:41,843]
INFO
{org.wso2.carbon.ldap.server.configuration.LDAPConfigurationBuilder} -
KDC server is disabled.
{org.wso2.carbon.ldap.server.configuration.LDAPConfigurationBuilder}
TID: [] [WSO2 Governance Registry] [2012-03-29 15:41:41,859] INFO
{org.wso2.carbon.ldap.server.DirectoryActivator} - Initializing
Directory Server with working directory
D:\Distr\WSO2greg\WSO2GR~1.1\WSO2GR~1.1\bin..\repository\data\org.wso2.carbon.directory
and port 10389 {org.wso2.carbon.ldap.server.DirectoryActivator} TID:
[] [WSO2 Governance Registry] [2012-03-29 15:41:50,265] ERROR
{org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache} - Failed to
insert resource to /. Не поддерживаемая функция
{org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache}
java.sql.SQLException: Не поддерживаемая функция at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
"

WSO2 Governance Registry(4.5.0 onward) supports for different encoding types
Eg:
If you want to use Governance Registry with Russian, you should start the server with proper encoding type.
Windows : wso2server.bat -Dcarbon.registry.character.encoding=windows-1251
Liux : sh wso2server.sh -Dcarbon.registry.character.encoding=windows-1251
More information : http://docs.wso2.org/wiki/display/Governance450/Supported+System+Properties

Related

WSO2 APIM 4 JMS Provider is not yet started

I'm getting the below error after starting a new WSO2 APIM 4 instance.
TID: [-1] [] [2022-01-09 09:19:45,277] ERROR {org.wso2.carbon.apimgt.common.jms.JMSListener} - JMS Provider is not yet started. Please start the JMS provider now.
TID: [-1] [] [2022-01-09 09:19:45,277] ERROR {org.wso2.carbon.apimgt.common.jms.JMSListener} - Connection attempt : 4 for JMS Provider failed. Next retry in 160 seconds
OS: CentOS 7.9
Java: OpenJDK 8
wso2apim version :4.0.0
I was using super admin password containing (#) issue resolved by removing the (#) from my admin password.
API amanger uses this password in connection strings to connect to JMS .

WSO2 EI 6.2.0 CAR deployment broken - NoClassDefFoundError

we have a project, where we have been using WSO2 Enterprise Integrator for a year or so. The implementation became relatively complex over time and it involves combination of proxies, APIs, templates, custom mediators and message broker. This gets deployed via a single CAR deployment artifact. The common code has been shared as WSO2>Extensions>JavaLibraryProject (WSO2 DevStudio). This library gets archived into CAR as:
<artifact name="M2E-Commons" version="1.0.1" type="lib/library/bundle" serverRole="ApplicationServer">
<file>M2E-Commons-1.0.1.jar</file>
</artifact>
This had been working for us just fine for all of the past releases, but got broken with WSO2 EI 6.2.0
This is the beginning of the log while deploying on WSO2 EI 6.1.1:
TID: [-1234] [] [2018-04-09 14:33:52,337] INFO {org.wso2.carbon.application.deployer.internal.ApplicationManager} - Deploying Carbon Application : M2E-CAP_1.0.16.car... {org.wso2.carbon.application.deployer.internal.ApplicationManager}
TID: [-1234] [] [2018-04-09 14:33:52,350] INFO {org.wso2.carbon.application.deployer.handler.DefaultAppDeployer} - OSGi bundle in file:///opt/wso2ei/wso2/tmp/carbonapps/-1234/1523284432337M2E-CAP_1.0.16.car/M2E-Commons_1.0.1/M2E-Commons-1.0.1.jar location is about to be installed to Carbon Server. {org.wso2.carbon.application.deployer.handler.DefaultAppDeployer}
TID: [-1234] [] [2018-04-09 14:33:52,351] INFO {org.wso2.carbon.application.deployer.handler.DefaultAppDeployer} - OSGi bundle M2E-Commons installed to Carbon Server. {org.wso2.carbon.application.deployer.handler.DefaultAppDeployer}
TID: [-1234] [] [2018-04-09 14:33:52,369] INFO {org.wso2.carbon.application.deployer.handler.DefaultAppDeployer} - OSGi bundle M2E-Commons successfully started on Carbon Server. {org.wso2.carbon.application.deployer.handler.DefaultAppDeployer}
TID: [-1234] [] [2018-04-09 14:33:52,369] INFO {org.apache.synapse.deployers.ClassMediatorDeployer} - Deploying Class mediators from file : /opt/wso2ei/wso2/tmp/carbonapps/-1234/1523284432337M2E-CAP_1.0.16.car/M2E-Device_1.0.0/M2E-Device-1.0.0.jar {org.apache.synapse.deployers.ClassMediatorDeployer}
TID: [-1234] [] [2018-04-09 14:33:52,370] INFO {org.apache.synapse.deployers.ClassMediatorDeployer} - Deploying Class mediators from file : /opt/wso2ei/wso2/tmp/carbonapps/-1234/1523284432337M2E-CAP_1.0.16.car/M2E-Flic_1.0.0/M2E-Flic-1.0.0.jar {org.apache.synapse.deployers.ClassMediatorDeployer}
And this is the same CAR deployed on WSO2 EI 6.2.0:
TID: [-1234] [] [2018-04-06 22:29:46,703] INFO {org.wso2.carbon.application.deployer.internal.ApplicationManager} - Deploying Carbon Application : M2E-CAP_1.0.16.car... {org.wso2.carbon.application.deployer.internal.ApplicationManager}
TID: [-1234] [] [2018-04-06 22:29:46,810] INFO {org.apache.synapse.deployers.ClassMediatorDeployer} - Deploying Class mediators from file : /opt/wso2ei/wso2/tmp/carbonapps/-1234/1523053786703M2E-CAP_1.0.16.car/M2E-Device_1.0.0/M2E-Device-1.0.0.jar {org.apache.synapse.deployers.ClassMediatorDeployer}
TID: [-1234] [] [2018-04-06 22:29:46,810] INFO {org.apache.synapse.deployers.ClassMediatorDeployer} - Deploying Class mediators from file : /opt/wso2ei/wso2/tmp/carbonapps/-1234/1523053786703M2E-CAP_1.0.16.car/M2E-Flic_1.0.0/M2E-Flic-1.0.0.jar {org.apache.synapse.deployers.ClassMediatorDeployer}
TID: [-1234] [] [2018-04-06 22:29:46,810] INFO {org.apache.synapse.deployers.ClassMediatorDeployer} - Deploying Class mediators from file : /opt/wso2ei/wso2/tmp/carbonapps/-1234/1523053786703M2E-CAP_1.0.16.car/M2E-M2L_ISS_1.0.0/M2E-M2L_ISS-1.0.0.jar {org.apache.synapse.deployers.ClassMediatorDeployer}
TID: [-1234] [] [2018-04-06 22:29:46,810] INFO {org.apache.synapse.deployers.ClassMediatorDeployer} - Deploying Class mediators from file : /opt/wso2ei/wso2/tmp/carbonapps/-1234/1523053786703M2E-CAP_1.0.16.car/M2E-M2T_1.0.1/M2E-M2T-1.0.1.jar {org.apache.synapse.deployers.ClassMediatorDeployer}
TID: [-1234] [] [2018-04-06 22:29:46,881] ERROR {org.apache.synapse.deployers.AbstractSynapseArtifactDeployer} - Deployment of the Synapse Artifact from file : /opt/wso2ei-6.2.0/wso2/tmp/carbonapps/-1234/1523053786703M2E-CAP_1.0.16.car/M2E-ISS.LightOff_1.0.0/M2E-ISS.LightOff-1.0.0.xml : Failed! {org.apache.synapse.deployers.AbstractSynapseArtifactDeployer}
java.lang.NoClassDefFoundError: sk/m2ms/wso2/m2e/M2Mediator
Apparently the OSGi bundle M2E-Commons deployment was not prioritized properly to start before the rest of artifact deployments - resulting in NoClassDefFoundError.
Do you have any ideas?
Can this be solved via some OSGi compliant mechanism/concept?
Or this is a valid bug to be submitted against WSO2?
Thank you in advance,
Peter
An error like NoClassDefFoundError will never happen because of start ordering. It means that a bundle uses the package sk.m2ms.wso2.m2e but neither imports nor contains that package. That is an error in the construction of the bundle, so if this is not a bundle that you built yourself then I would suggest that this is indeed a bug that should be reported to the vendor.

WSO2 API Manager 2.1 Analytics cannot be restarted when using Oracle DB

When restarting APIM Analytics the following error appears in log (the first run is ok). We need to truncate ANX___8GEKYOMM_ table for being able to start it again.
TID: [-1234] [] ERROR {org.wso2.carbon.analytics.dataservice.core.AnalyticsDataServiceComponent} - Error in activating analytics data service: null {org.wso2.carbon.analytics.dataservice.core.AnalyticsDataServiceComponent}
java.lang.RuntimeException
at org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore$RDBMSResultSetIterator.next(RDBMSAnalyticsRecordStore.java:881)
at org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore$RDBMSResultSetIterator.hasNext(RDBMSAnalyticsRecordStore.java:843)
at org.apache.commons.collections.IteratorUtils.toList(IteratorUtils.java:848)
at org.apache.commons.collections.IteratorUtils.toList(IteratorUtils.java:825)
at org.wso2.carbon.analytics.datasource.core.util.GenericUtils.listRecords(GenericUtils.java:284)
at org.wso2.carbon.analytics.dataservice.core.AnalyticsDataServiceImpl.readTenantIds(AnalyticsDataServiceImpl.java:468)
Caused by: java.lang.NullPointerException
at java.io.OutputStream.write(OutputStream.java:75)
at org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore$RDBMSResultSetIterator.extractDataFromRS(RDBMSAnalyticsRecordStore.java:890)
at org.wso2.carbon.analytics.datasource.rdbms.RDBMSAnalyticsRecordStore$RDBMSResultSetIterator.next(RDBMSAnalyticsRecordStore.java:863)
... 124 more
I have solved it upgrading from org.wso2.carbon.analytics.datasource.rdbms-1.3.0.jar to org.wso2.carbon.analytics.datasource.rdbms-1.3.6.jar

The console page is not coming for WSO2am 1.9.1 server started in CentOS 6

I am trying to install and use the WSO2 API management in CentOS6. I was able to install and start the server but the management console page is not up in the browser.The url for console is also different than the localhost as below
[2016-02-02 16:56:53,465] INFO - StartupFinalizerServiceComponent WSO2 Carbon started in 33 sec
[2016-02-02 16:56:53,549] INFO - StatisticsServiceComponent BAM Service Stat Publishing is disabled
[2016-02-02 16:56:53,969] INFO - CarbonUIServiceComponent Mgt Console URL : https://172.17.42.1:9443/carbon/
[2016-02-02 16:56:53,970] INFO - CarbonUIServiceComponent API Publisher Default Context : http://172.17.42.1:9763/publisher
[2016-02-02 16:56:53,970] INFO - CarbonUIServiceComponent API Store Default Context : http://172.17.42.1:9763/store
[2016-02-02 16:56:54,244] INFO - DefaultKeyValidationHandler org.wso2.carbon.apimgt.keymgt.handlers.DefaultKeyValidationHandler Initialised
[2016-02-02 16:56:54,244] INFO - APIKeyValidationService Initialised KeyValidationHandler instance successfully
[2016-02-02 16:56:54,245] INFO - APIKeyMgtServiceComponent Setting default carbon host for thrift key management service: 172.17.42.1
[2016-02-02 16:56:54,267] INFO - APIKeyMgtServiceComponent Started thrift key mgt service at port:10397
The console here shows to have started at https://172.17.42.1:9443/carbon/ whereas the host is different in which the server is running.
Did you encounter any errors during the start up?
The reason for having a different host IP could be due to the availability of multiple network interfaces on your CentOS machine.
Also verify whether the relevant ports are opened on your CentOS6 instance. Ref.

Gives error while trying to upload rule service in Business Rules Server, WSO2

I am trying to upload a .aar file in the management console of Business rules server, but while uploading i am getting this error: TID: [] [WSO2 BRS] [2013-02-19 18:41:29,556] ERROR {org.wso2.carbon.rulecep.service.RuleCEPDeployerService} - Can not build the service {org.wso2.carbon.rulecep.service.RuleCEPDeployerService}
java.util.MissingResourceException: Can't find resource for bundle org.apache.axis2.i18n.ProjectResourceBundle, key The operation is not valid: operation name missing
at java.util.ResourceBundle.getObject(ResourceBundle.java:374)
at java.util.ResourceBundle.getString(ResourceBundle.java:334)
at org.apache.axis2.i18n.MessageBundle.getMessage(MessageBundle.java:194)
at org.apache.axis2.i18n.MessageBundle.getMessage(MessageBundle.java:83)
at org.apache.axis2.i18n.Messages.getMessage(Messages.java:74)
at org.apache.axis2.deployment.ServiceBuilder.processOperations(ServiceBuilder.java:717)
at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:355)
at org.wso2.carbon.rulecep.service.ServiceBuilder.createAxisService(ServiceBuilder.java:266)
at org.wso2.carbon.rulecep.service.ServiceBuilder.build(ServiceBuilder.java:146)
at org.wso2.carbon.rulecep.service.RuleCEPDeployerService.deploy(RuleCEPDeployerService.java:77)
at org.wso2.carbon.rule.service.RuleServiceDeployer.deploy(RuleServiceDeployer.java:69)
at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:813)
at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:371)
at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:365)
at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:73)
at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:94)
at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:93)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
TID: [] [WSO2 BRS] [2013-02-19 18:41:29,572] INFO {org.apache.axis2.deployment.DeploymentEngine} - org.apache.axis2.deployment.DeploymentException: Can't find resource for bundle org.apache.axis2.i18n.ProjectResourceBundle, key The operation is not valid: operation name missing {org.apache.axis2.deployment.DeploymentEngine}
TID: [] [WSO2 BRS] [2013-02-19 18:41:29,572] INFO {org.apache.axis2.deployment.DeploymentEngine} - org.apache.axis2.deployment.DeploymentException: Can't find resource for bundle org.apache.axis2.i18n.ProjectResourceBundle, key The operation is not valid: operation name missing {org.apache.axis2.deployment.DeploymentEngine}
try this method: http://wso2.com/library/articles/2013/05/eclipse-plugin-wso2-business-rules-server
I used to have problems similar to yours while uploading the .aar files through the wizard, but I followed the above tutorial and it works perfectly fine.