Hi all,
I am getting some strange errors while starting up the WSO2 6.1.1 server. Hope
that you can help.
So, I have a single node WSO2 Server running and connecting to a RabbitMQ node
(rmqNode1) that is part of a cluster of two (rmqNode1 and rmqNode2).
Have in mind that all the transportSender and listeners are pointing to
rmqNode1. No connection details are defined for rmqNode2.
If I have the two RabbitMQ cluster nodes up and running and start the WSO2
6.1.1 server there isn’t any issue.
With all servers up, if I shutdown rmqNode2, all continues ok with no errors.
If I only have rmqNode1 up and then start WSO2 6.1.1, I get a endless stream of
errors like :
TID: [-1] [] [2017-11-02 15:34:48,232] ERROR
{org.apache.axis2.transport.rabbitmq.ServiceTaskManager} - Error, Connection
already closed myProxysample, Listner id - 78
{org.apache.axis2.transport.rabbitmq.ServiceTaskManager}
com.rabbitmq.client.AlreadyClosedException: channel is already closed due to
channel error; protocol method: #method<channel.close>(reply-code=404,
reply-text=NOT_FOUND - home node '[email protected]' of durable queue
’sample.queue' in vhost ’sample' is down or inaccessible, class-id=50,
method-id=10)
at com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:198)
at com.rabbitmq.client.impl.AMQChannel.rpc(AMQChannel.java:244)
at com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:222)
at
com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:117)
at com.rabbitmq.client.impl.ChannelN.queueDeclare(ChannelN.java:925)
at
com.rabbitmq.client.impl.recovery.AutorecoveringChannel.queueDeclare(AutorecoveringChannel.java:332)
at
org.apache.axis2.transport.rabbitmq.utils.RabbitMQUtils.declareQueue(RabbitMQUtils.java:213)
at
org.apache.axis2.transport.rabbitmq.ServiceTaskManager$MessageListenerTask.initConsumer(ServiceTaskManager.java:527)
at
org.apache.axis2.transport.rabbitmq.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:335)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
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)
TID: [-1234] [] [2017-11-02 15:34:48,267] INFO
{org.apache.tomcat.util.net.NioSelectorPool} - Using a shared selector for
servlet write/read {org.apache.tomcat.util.net.NioSelectorPool}
TID: [-1] [] [2017-11-02 15:34:48,303] INFO
{org.apache.axis2.transport.rabbitmq.ServiceTaskManager} - Successfully
reconnected to RabbitMQ Broker for the service myProxysampleSecond, Listner id
- 78 {org.apache.axis2.transport.rabbitmq.ServiceTaskManager}
TID: [-1] [] [2017-11-02 15:34:48,243] ERROR
{org.apache.axis2.transport.rabbitmq.ServiceTaskManager} - Error, Connection
already closed STD.cacheXRefReceiver.1.0.0, Listner id - 77
{org.apache.axis2.transport.rabbitmq.ServiceTaskManager}
com.rabbitmq.client.AlreadyClosedException: channel is already closed due to
channel error; protocol method: #method<channel.close>(reply-code=404,
reply-text=NOT_FOUND - home node '[email protected]' of durable queue
’second.sample.queue' in vhost 'sample' is down or inaccessible, class-id=50,
method-id=10)
at com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:198)
Please note that node2.site1 is the hostname for rmqNode2.
I don’t think the server should complain about this. The node that is used on
the transport configuration is always node1.
Any ideias on what may be incorrect? Or can be done ?
I didn’t find any connection parameter that is related to cluster setup, is
there any?
Many thanks in advance.
Norberto_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
