I'm using the prepackaged IDS 5.3.0 as a key manager. When I restart or start the server it always stops for a while on part of start-up, as shown below. I can't really find a solid answer in any of the documentation about it. I never had the older versions do this. I was just curious if I can get rid of this warning.
INFO {org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent} - PKCE Support enabled.
TID: [-1] [] [2017-03-06 14:11:26,275] WARN {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Waiting for required OSGi services: org.wso2.carbon.server.admin.common.IServerAdmin,
Related
I have a wso2apimanager-4.1.0 with the role of control-plane. In the wso2carbon.log, the following stack trace keeps appearing, especially when I try to deploy an API change. The main errors are "Caused by: org.wso2.andes.AMQConnectionFailureException: Server did not respond in a timely fashion [error code 408: Request Timeout]" and "ERROR {org.wso2.andes.client.AMQConnection} - Throwable Received but no listener set. org.wso2.andes.AMQDisconnectedException: Server closed connection and reconnection not permitted."
error_1
error_2
Despite these errors, the gateway-workers can connect to the control-plane on startup pulling all the APIs deployed on the API Manager ecosystem. Although, when I deploy a new version of an API, the gateways are not notified (because the JMS is down) and they do not pull the changes until they are rebooted.
I've already reviewed the jndi.properties, user-mgt.xml and all the superuser username and password are correct (they are pulled from deployment.toml correctly). The JMS port exists when the control-plane service starts and is not being blocked by any firewall, also the superuser password doesn't have special characters like '#'.
I've migrated the control-plane from version 4.0.0 to version 4.1.0 recently, the error did not occur in 4.0.0. The config file (deployment.toml) is the same.
Has anyone come across this problem? How can I resolve this error?
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>
I downloaded and installed the WSO2 API Manager version 1.4.0 yesterday and I cannot login to the web management console (https://localhost:9443/carbon) using the default credentials (i.e. admin/admin)
I can login to the API store and API publisher and the error comes only for the management console.
Note that I performed the default install (unzip and ran ./wso2server.sh from the bin folder)
Following is part of the error stacktrace
2013-06-03 15:42:13,095] INFO - CarbonAuthenticationUtil 'admin#carbon.super [-1234]' logged in at [2013-06-03 15:42:13,095+1000]
[2013-06-03 15:42:13,112] ERROR - AuthenticationHandler System error : 0 active authenticators registered in the system. The system should have at least 1 active authenticator service registered.
java.lang.RuntimeException: System error : 0 active authenticators registered in the system. The system should have at least 1 active authenticator service registered.
at org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.isAuthenticated(AuthenticationHandler.java:144)
at org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:83)
Further down the stacktrace, I also get the below
[2013-06-04 11:42:15,860] ERROR - AxisEngine Authentication failure
org.apache.axis2.AxisFault: Authentication failure
at org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:110)
at org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:55)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
I also get the following two warning messages on startup
[2013-06-04 11:14:05,489] WARN - ValidationResultPrinter Swap Memory size (MB): 64 of the system is below the recommended minimum size :2048
[2013-06-04 11:14:15,444] WARN - LandingPageWebappDeployer Product landing page not found.
#nuwandias Hi Nuwan.
I identified the issue. When I was evaluating the previous 1.3.1 version, I injected the Authorization header with the Bearer token via my Firefox browser plugin.
That was what caused the problem with the 1.4.0 version. Once I disable it it works fine.
All good now and I am looking forward to doing a deep dive evaluation of this product.
Thanks a lot for your support.
I have just downloaded the zip from the website and tried the same and it worked fine. Can you please provide the following information.
What is the environment that you are trying this on (OS)?
What is the md5sum value of the zip archive? Mine is fea68eaadd17daa5e6fa0aff3d973601.
Do you see any errors/warnings on startup? If so, could you share the startup logs too?
Thanks,
Nuwan.
Looking at this log message...
Swap Memory size (MB): 64 of the system is below the recommended minimum size :2048
It seems like your hard drive (or partition) has filled up. I'm wondering whether this could have caused any errors when you unzipped the zip file (if the hard disk has no free space).
If this is the case, can you free up some space (>200MB) in your partition, unzip the archive again and retry?
Using WSO2 API Manager 1.3 and WSO2 BAM 2.0.
I followed the instructions found in the README.txt in /statistics.
I am getting the following error when starting API Manager:
TID: [0] [AM] [2013-05-02 11:42:44,239] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Any suggestions on where to start looking for the issue?
It looks like you have not properly configured WSO2 API Manager 1.3 to work with WSO2 BAM.
For proper configuration follow the official docs[1]
This issue might also occur When you set an offset to BAM by 1 as described in the README.txt, as it needs its Cassandra DB configurations to be changed for the offset by 1 at BAM_HOME/repository/conf/etc/cassandra-component.xml. Therefore follow the like provided[1] where we change the API Manager's offset.
Suho
[1]http://docs.wso2.org/wiki/display/AM130/Monitoring+and+Statistics
I got the following error when runnning WSO2 API Manager 1.3.1 to use the WSO2 BAM Server 2.0.1.
TID: [0] [AM] [2013-05-02 18:58:40,609] ERROR
{org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
- Error initializing APIMgtUsageDataBridgeDataPublisher {org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageDataBridgeDataPublisher}
org.wso2.carbon.databridge.agent.thrift.exception.AgentException:
Error when finding event stream definition for :
org.wso2.apimgt.statistics.request 1.0.0
Both API Manager and BAM are running on the same machine and I changed offset to 1 in /home/jtao/api/wso2bam-2.0.1/repository/conf/carbon.xml based on Monetization of API Usage.
I also checked that BAM_HOME/repository/conf/etc/cassandra-component.xml doesn't exist in BAM 2.0.1. as someone suggested in the answer of another question "Configuring WSO2 API Manager to use the WSO2 BAM Server"
Any ideas?
I ran the same scenario described in guide and it works without any error. May be your have missed a part in the configuration guide? Make sure BAM_HOME is set correctly and BAM server is started before the AM server.
The following guide too can be used to integrate AM 1.3.1 with BAM 2.0.1
http://docs.wso2.org/wiki/display/AM131/Monitoring+and+Statistics
Ishara