We have had customers using HornetQ on Jboss 6.x complaining about tasks remaining "In Progress" and not finishing up.
We came across the following log errors relating to HornetQ (the JBoss 6.x JMS service engine):
2014-04-29 09:22:39,191 ERROR [org.hornetq.core.server] (Thread-15 (HornetQ-client-global-threads-14697284)) HQ224037: cluster connection Failed to handle message: java.lang.IllegalStateException: Cannot find binding for 67525023-210b-415d-8de6-682ed6242b32c3a2bdc6-cfa6-11e3-9c4c-2dfb60f4786c at
org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecord Impl.doConsumerClosed(ClusterConnectionImpl.java:1570) [hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1] at org.hornetq.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecord Impl.onMessage(ClusterConnectionImpl.java:1288)
[hornetq-server-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1] at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumer Impl.java:1085)
[hornetq-core-client-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1] at org.hornetq.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImp l.java:57)
[hornetq-core-client-2.3.1.Final-redhat-1.jar:2.3.1.Final-redhat-1]
Correcting the issue required a good examination of the cluster setup and multicast defnitions located in the standalone-full-ha.xml. Below is an example of that file section. The details in this example are not necessarily going to apply to your situation , however, the idea and the relationship between these values should:
<socket-binding multicast-address="${jboss.default.multicast.address:230.0.0.5}"
multicast-port="45701" name="jgroups-mping" port="0"/>
<socket-binding name="jgroups-tcp" port="7600"/>
<socket-binding name="jgroups-tcp-fd" port="57600"/>
<socket-binding multicast-address="${jboss.default.multicast.address:230.0.0.5}"
multicast-port="45689" name="jgroups-udp" port="55201"/>
<socket-binding name="jgroups-udp-fd" port="54201"/>
<socket-binding name="messaging" port="5445"/>
<socket-binding multicast-address="${jboss.messaging.group.address:231.7.7.8}"
multicast-port="${jboss.messaging.group.port:9877}" name="messaging-group" port="0"/>
<socket-binding name="messaging-throughput" port="5455"/>
<socket-binding multicast-address="224.0.1.106" multicast-port="23365" name="modcluster" port="0"/>
Yours,
Sagi Gabay,
CA Technologies.