I just installed an Active-Active Deployment APIM-2.6 (2 nodes with same 
configs).
Both servers share a common <API-M_HOME>/repository/deployment/server 
directory, and both start with no errors/warnings.
I can publish and test APIs, on any of one of the 2 servers, it's ok, but in my 
logs I find this error reported below.  


TID: [-1234] [] [2019-07-31 11:00:33,809]  INFO 
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Local entry : 
gov:/apimgt/statistics/ga-config.xml was added to the Synapse configuration 
successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
TID: [-1234] [] [2019-07-31 11:00:33,833]  INFO 
{org.apache.synapse.core.axis2.TimeoutHandler} -  This engine will expire all 
callbacks after GLOBAL_TIMEOUT: 120 seconds, irrespective of the timeout 
action, after the specified or optional timeout 
{org.apache.synapse.core.axis2.TimeoutHandler}
TID: [-1] [] [2019-07-31 11:00:33,918]  INFO 
{org.wso2.carbon.databridge.core.DataBridge} -  user admin connected 
{org.wso2.carbon.databridge.core.DataBridge}
TID: [-1234] [] [2019-07-31 11:00:33,955]  INFO 
{org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory} - 
 JMS ConnectionFactory : jmsEventPublisher initialized 
{org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory}
TID: [-1234] [] [2019-07-31 11:00:33,988]  INFO 
{org.wso2.andes.server.handler.ConnectionStartOkMethodHandler} -  SASL 
Mechanism selected: PLAIN 
{org.wso2.andes.server.handler.ConnectionStartOkMethodHandler}
TID: [-1234] [] [2019-07-31 11:00:33,989]  INFO 
{org.wso2.andes.server.handler.ConnectionStartOkMethodHandler} -  Locale 
selected: en_US {org.wso2.andes.server.handler.ConnectionStartOkMethodHandler}
TID: [-1234] [] [2019-07-31 11:00:34,026]  INFO 
{org.wso2.andes.server.handler.ConnectionStartOkMethodHandler} -  
Authentication failed:Error processing data: javax.security.sasl.SaslException: 
Authentication failed 
{org.wso2.andes.server.handler.ConnectionStartOkMethodHandler}
TID: [-1] [] [2019-07-31 11:00:34,027]  INFO 
{org.wso2.andes.client.handler.ConnectionCloseMethodHandler} -  ConnectionClose 
frame received {org.wso2.andes.client.handler.ConnectionCloseMethodHandler}
TID: [-1] [] [2019-07-31 11:00:34,028]  INFO 
{org.wso2.andes.client.handler.ConnectionCloseMethodHandler} -  Error :530: not 
allowed:Thread-54 {org.wso2.andes.client.handler.ConnectionCloseMethodHandler}
TID: [-1] [] [2019-07-31 11:00:34,028]  INFO 
{org.wso2.andes.server.handler.ConnectionCloseOkMethodHandler} -  Received 
Connection-close-ok 
{org.wso2.andes.server.handler.ConnectionCloseOkMethodHandler}
TID: [-1] [] [2019-07-31 11:00:34,028]  INFO 
{org.wso2.andes.client.state.AMQStateManager} -  Notifying 
Waiters([org.wso2.andes.client.state.StateWaiter@62b8f2fe]) for error:not 
allowed {org.wso2.andes.client.state.AMQStateManager}
TID: [-1] [] [2019-07-31 11:00:34,030] ERROR 
{org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory} - 
 Error acquiring a Connection from the JMS CF : jmsEventPublisher using 
properties : {transport.jms.ConcurrentPublishers=allow, 
java.naming.provider.url=repository/conf/jndi.properties, 
java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory,
 transport.jms.DestinationType=topic, 
transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactory, 
transport.jms.Destination=throttleData} 
{org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory}
javax.jms.JMSException: Error creating connection: Unable to Connect
        at 
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:346)
        at 
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:53)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSUtils.createConnection(JMSUtils.java:387)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory.createConnection(JMSConnectionFactory.java:268)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory$PoolableJMSConnectionFactory.makeObject(JMSConnectionFactory.java:356)
        at 
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1181)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory.getConnectionFromPool(JMSConnectionFactory.java:286)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSMessageSender.send(JMSMessageSender.java:86)
        at 
org.wso2.carbon.event.output.adapter.jms.JMSEventAdapter$JMSSender.run(JMSEventAdapter.java:284)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: org.wso2.andes.AMQConnectionFailureException: Unable to Connect
        at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:485)
        at 
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:328)
        ... 13 more
TID: [-1] [] [2019-07-31 11:00:34,031]  WARN 
{org.wso2.andes.client.state.AMQStateManager} -  No Waiters for error saving as 
last error:Exception thrown against AMQConnection:
Host: localhost
Port: 5672
Virtual Host: carbon
Client ID: clientid
Active session count: 0: org.wso2.andes.AMQDisconnectedException: Server closed 
connection and reconnection not permitted. 
{org.wso2.andes.client.state.AMQStateManager}
TID: [-1] [] [2019-07-31 11:00:34,032] ERROR 
{org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory} - 
 Error acquiring a Connection from the JMS CF : jmsEventPublisher using 
properties : {transport.jms.ConcurrentPublishers=allow, 
java.naming.provider.url=repository/conf/jndi.properties, 
java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory,
 transport.jms.DestinationType=topic, 
transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactory, 
transport.jms.Destination=throttleData} 
{org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory}
org.wso2.carbon.event.output.adapter.core.exception.OutputEventAdapterRuntimeException:
 Error acquiring a Connection from the JMS CF : jmsEventPublisher using 
properties : {transport.jms.ConcurrentPublishers=allow, 
java.naming.provider.url=repository/conf/jndi.properties, 
java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory,
 transport.jms.DestinationType=topic, 
transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactory, 
transport.jms.Destination=throttleData}
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory.handleException(JMSConnectionFactory.java:197)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory.createConnection(JMSConnectionFactory.java:278)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory$PoolableJMSConnectionFactory.makeObject(JMSConnectionFactory.java:356)
        at 
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1181)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory.getConnectionFromPool(JMSConnectionFactory.java:286)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSMessageSender.send(JMSMessageSender.java:86)
        at 
org.wso2.carbon.event.output.adapter.jms.JMSEventAdapter$JMSSender.run(JMSEventAdapter.java:284)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: javax.jms.JMSException: Error creating connection: Unable to Connect
        at 
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:346)
        at 
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:53)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSUtils.createConnection(JMSUtils.java:387)
        at 
org.wso2.carbon.event.output.adapter.jms.internal.util.JMSConnectionFactory.createConnection(JMSConnectionFactory.java:268)
        ... 10 more
Caused by: org.wso2.andes.AMQConnectionFailureException: Unable to Connect
        at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:485)
        at 
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:328)
        ... 13 more
TID: [-1] [] [2019-07-31 11:00:34,032]  WARN 
{org.wso2.andes.client.AMQConnection} -  Throwable Received but no listener 
set: org.wso2.andes.AMQDisconnectedException: Server closed connection and 
reconnection not permitted. {org.wso2.andes.client.AMQConnection}
TID: [-1] [] [2019-07-31 11:00:34,034]  WARN 
{org.wso2.andes.client.AMQConnection} -  Throwable Received but no listener 
set: org.wso2.andes.AMQException: AMQP timed out when attempting to close the 
connection  {org.wso2.andes.client.AMQConnection}




Since the error (I don't undestand) related to a connection to Port: 5672, I 
checked the log at start up but all seems ok:
TID: [-1234] [] [2019-07-31 09:47:28,446]  INFO {qpid.message.broker.listening} 
-  [Broker] BRK-1002 : Starting : Listening on TCP port 5672 
{qpid.message.broker.listening}
TID: [-1] [] [2019-07-31 09:47:28,448]  INFO 
{org.wso2.andes.kernel.AndesContextInformationManager} -  Queue Sync [create]: 
deadletterchannel {org.wso2.andes.kernel.AndesContextInformationManager}
TID: [-1234] [] [2019-07-31 09:47:28,452]  INFO {qpid.message.broker.listening} 
-  [Broker] BRK-1002 : Starting : Listening on TCP/SSL port 8672 
{qpid.message.broker.listening}
TID: [-1234] [] [2019-07-31 09:47:28,457]  INFO 
{org.wso2.carbon.andes.internal.QpidServiceComponent} -  AMQP Host Address : 
0.0.0.0 Port : 5672 {org.wso2.carbon.andes.internal.QpidServiceComponent}
TID: [-1234] [] [2019-07-31 09:47:28,457]  INFO 
{org.wso2.carbon.andes.internal.QpidServiceComponent} -  Successfully connected 
to AMQP server on port 5672 
{org.wso2.carbon.andes.internal.QpidServiceComponent}


The error is being logged on the server where a new API publication has been 
created,  at the moment the API is being called for the first time. 

Bernard


_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to