Wso2am - Error in creating and login in tenants - wso2

I am trying to create multiple tenants in a wso2am (1.10) installation.
When i create the tenant i get the following error "Failed to add tenant config" with the following exception
TID: [-1234] [] [2017-02-01 13:23:58,740] ERROR {org.wso2.carbon.tenant.mgt.ui.utils.TenantMgtUtil} - Failed to add tenant config. tenant-domain: public.xxxxx, tenant-admin: admin. {org.wso2.carbon.tenant.mgt.ui.utils.TenantMgtUtil}
org.apache.axis2.AxisFault: Could not initialize class org.wso2.carbon.utils.i18n.Messages
Nevertheless when i try to enable the tenant it gets enabled and the required folders are created.
Unfortunately the tenants are not usable. On my first login i get the same exception
TID: [6] [] [2017-02-01 13:26:40,577] admin#remote.gunet [6] [AM]ERROR {org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient} - Error occurred while logging in {org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient}
org.apache.axis2.AxisFault: Could not initialize class org.wso2.carbon.utils.i18n.Messages
I have tried a clean installation of the server but that had no effect.
Is there some official guideline for the specific problem?

Fixed the keystore and the matter was resolved.

Related

WSO2 Identity Server: Authorization failure caused by Thread Death

I have a WSO2 Identity Server 5.3.0 installation configured with a read-only LDAP user store following: https://docs.wso2.com/display/IS570/Configuring+a+Read-only+LDAP+User+Store
This is the (edited) user-mgt.xml: https://pastebin.com/qy9PGbnP
The setup works for a while, but after some time (around 6 or more hours) I get the following error whenever any user tries to login.
TID: [-1234] [] [2018-12-12 08:35:21,895] ERROR {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} - Error occurred while accessing Java Security Manager Privilege Block
Full trace: https://pastebin.com/yhEBQE4V
Since this issue is hard to reproduce (I have to wait until it happens again after restarting). Is there anything that could help me debug this issue?
It was a firewall between the application server and the database.
Problem solved after adding these parameters to the master-datasources.xml
<maxAge>1800000</maxAge>
<timeBetweenEvictionRunsMillis>750000</timeBetweenEvictionRunsMillis>
<minEvictableIdleTimeMillis>750000</minEvictableIdleTimeMillis>

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

Error occurred while getting the APIs

I locally installed WSO2 API manager and create API but API list is not coming at WSO2 dashboard . It displaying an error i.e
[2015-11-03 18:47:29,781] ERROR - AsyncDataPublisher Reconnection failed for for tcp://localhost:7614"
index:jag org.wso2.carbon.apimgt.api.APIManagementException: Error occurred while getting the APIs
Version of API manager is 1.9.1
I can't get any API statistics
This issue can be occurred when you have not configured information according to the Port Offset value. As an example if the port offset value of BAM instance is 3,need to configure as follows in property in the api-manager.xml which is in /repository/conf/ folder.
<ThriftPort>7614</ThriftPort>
<BAMServerURL>{tcp://<IP Address>:7614/}</BAMServerURL>
Also make sure to restart both servers.

WSO2API Manager : Api Store Error: Error in getting new access token

I have updated WSO2 default SLL with the custom SSL certificate on my Production Server on which WSO2Api installed.
SSL issues have been fixed, but now I am getting error while re-generating access token
Logs
Caused by: org.wso2.carbon.apimgt.keymgt.APIKeyMgtException: Error in getting new accessToken
at org.wso2.carbon.apimgt.keymgt.service.APIKeyMgtSubscriberService.renewAccessToken(APIKeyMgtSubscriberService.java:281)
... 45 more
Caused by: java.lang.RuntimeException: Failed : HTTP error code : 500
at org.wso2.carbon.apimgt.keymgt.service.APIKeyMgtSubscriberService.renewAccessToken(APIKeyMgtSubscriberService.java:252)
... 45 more
TID: [0] [AM] [2014-08-27 10:57:41,440] ERROR {org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject} - Error in getting new accessToken {org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject}
If APIManager runs with a port offset,you need to do addtional changes.
Change the endpoint ports defined in default APIs shipped with APIManager
Find all default APIs of the API Manager in /repository/deployment/server/synapse-configs/default/api folder. Those are Authorize API, Login API, Token API and Revoke API. Open each of them and change the address endpoint config included port value to match with offset value.The default address endpoint config is
"address uri="https://192.168.1.7:9443/oauth2/token".If the AM standalone pack running with port offset 2 change that config as
address uri="https://192.168.1.7:9445/oauth2/token"
What I did to fix the issue was to 1) add admin user inside ApiKeyValidaor in api-manager.xml also into admin user via management console and into user-mgt.xml; 2) Inside api-manager.xml:
Change the following:
https://${carbon.local.ip}:${mgt.transport.https.port}${carbon.context}/services/
to:
https://[FQDN_OF_HOST}:${mgt.transport.https.port}${carbon.context}/services/
Reason is my server certificate only recorded the domain name, not ip address.
My setup: Product: WSO2 AM 1.10.0 DB: MSSQL Security: SAML2 integrated with PingIdentity OS: Linux
Please also refer to this question:
wso2 am 1.10.0 API Store: "Error occurred while executing the action generateApplicationKey" with " Invalid credentials provided."
The error may be due to one of these two things:
Your admin password is not set for ApiKeyManager in api_manager.xml.
SSL is not set properly.

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.