There are two causes for this error message:
If you see this error message as a one-off message while server nodes of your clusters are starting, then the error can be ignored.
If you continuously see this error in the logs, this signifies that Wildfly's JMS queue became corrupted after an improper shutdown (kill -9 or JVM/server crash). It won't always happen after an improper shutdown, but it's fairly common. Any of the JMS queues could be impacted by this. Depending on the JMS queue impacted and the Assure features used in your controls, there could be no impact or a widespread impact.
A redeploy will rebind the queues and resolve the issue.
Sample error message:
2019-08-31 00:00:05,714 ERROR [org.apache.activemq.artemis.core.server] (Thread-15 (ActiveMQ-client-global-threads-1192705745)) AMQ224037: cluster connection Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue.IA_CASAPIInputQueuec10b1b06-ca43-11e8-b919-13fa3d7b1337
at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerClosed(ClusterConnectionImpl.java:1319)
at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.handleNotificationMessage(ClusterConnectionImpl.java:1005)
at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:974)
at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1018)
at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:48)
at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1145)
at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Comments
1 comment
Just wanted to put the comments by the customer, in their case, redeploy did not rebind the queues but restarting the JVMs did. So it is better to restart the JVMs first before attempting to redeploy.
Please sign in to leave a comment.