wildfly - HQ224037: cluster connection Failed to handle message - See more at: https://developer.jboss.org/message/934562#934562 -

we seeing below error in hornetq cluster configurations.

2015-06-25 07:11:45,425 error (thread-0 (hornetq-client-global-threads-1606034117)) [org.hornetq.core.server] hq224037: cluster connection failed handle message: java.lang.illegalstateexception: cannot find binding jms.queue.icp.enterprisef191140e-154d-11e5-aba6-29ed79c6c396 on clusterconnectionimpl@1994957667[nodeuuid=44207bc3-154e-11e5-a8b5-2752befdd59f, connector=transportconfiguration(name=http-connector, factory=org-hornetq-core-remoting-impl-netty-nettyconnectorfactory) ?port=8080&host=apsed3096&http-upgrade-enabled=true&http-upgrade-endpoint=http-acceptor, address=jms.queue.icp, server=hornetqserverimpl::serveruuid=44207bc3-154e-11e5-a8b5-2752befdd59f] @ org.hornetq.core.server.cluster.impl.clusterconnectionimpl$messageflowrecordimpl.doconsumercreated(clusterconnectionimpl.java:1426) [hornetq-server-2.4.5.final.jar:] @ org.hornetq.core.server.cluster.impl.clusterconnectionimpl$messageflowrecordimpl.handlenotificationmessage(clusterconnectionimpl.java:1163) [hornetq-server-2.4.5.final.jar:] @ org.hornetq.core.server.cluster.impl.clusterconnectionimpl$messageflowrecordimpl.onmessage(clusterconnectionimpl.java:1131) [hornetq-server-2.4.5.final.jar:] @ org.hornetq.core.client.impl.clientconsumerimpl.callonmessage(clientconsumerimpl.java:1116) [hornetq-core-client-2.4.5.final.jar:] @ org.hornetq.core.client.impl.clientconsumerimpl.access$500(clientconsumerimpl.java:56) [hornetq-core-client-2.4.5.final.jar:] @ org.hornetq.core.client.impl.clientconsumerimpl$runner.run(clientconsumerimpl.java:1251) [hornetq-core-client-2.4.5.final.jar:] @ org.hornetq.utils.orderedexecutorfactory$orderedexecutor$1.run(orderedexecutorfactory.java:104) [hornetq-core-client-2.4.5.final.jar:] @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1142) [rt.jar:1.8.0_40] @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:617) [rt.jar:1.8.0_40] @ java.lang.thread.run(thread.java:745) [rt.jar:1.8.0_40] 

and here hornetq-configurations

<hornetq-server>                 <persistence-enabled>true</persistence-enabled>                 <security-enabled>false</security-enabled>                 <cluster-user>icp</cluster-user>                 <cluster-password>ingenix1</cluster-password>                 <transaction-timeout>306000</transaction-timeout>                 <shared-store>false</shared-store>                 <journal-type>nio</journal-type>                 <journal-file-size>102400</journal-file-size>                 <journal-min-files>2</journal-min-files>                 <connectors>                     <http-connector name="http-connector" socket-binding="http">                         <param key="http-upgrade-endpoint" value="http-acceptor"/>                     </http-connector>                     <in-vm-connector name="in-vm" server-id="0"/>                 </connectors>                 <acceptors>                     <http-acceptor http-listener="default" name="http-acceptor"/>                     <in-vm-acceptor name="in-vm" server-id="0"/>                 </acceptors>                 <broadcast-groups>                     <broadcast-group name="icp-broadcast-group">                         <jgroups-stack>tcpping</jgroups-stack>                         <connector-ref>                             http-connector                         </connector-ref>                     </broadcast-group>                 </broadcast-groups>                 <discovery-groups>                     <discovery-group name="icp-discovery-group">                         <jgroups-stack>tcpping</jgroups-stack>                     </discovery-group>                 </discovery-groups>                 <cluster-connections>                     <cluster-connection name="icp-cluster">                         <address>jms.queue.icp</address>                         <connector-ref>http-connector</connector-ref>                         <retry-interval>500</retry-interval>                         <use-duplicate-detection>true</use-duplicate-detection>                         <forward-when-no-consumers>true</forward-when-no-consumers>                         <max-hops>1</max-hops>                         <discovery-group-ref discovery-group-name="icp-discovery-group"/>                     </cluster-connection>                     <cluster-connection name="claimmap-cluster">                         <address>jms.queue.claimmap</address>                         <connector-ref>http-connector</connector-ref>                         <retry-interval>500</retry-interval>                         <use-duplicate-detection>true</use-duplicate-detection>                         <forward-when-no-consumers>true</forward-when-no-consumers>                         <max-hops>1</max-hops>                         <discovery-group-ref discovery-group-name="icp-discovery-group"/>                     </cluster-connection>                     <cluster-connection name="hornetq-internal-cluster">                         <address>hornetq.#</address>                         <connector-ref>http-connector</connector-ref>                         <retry-interval>500</retry-interval>                         <use-duplicate-detection>true</use-duplicate-detection>                         <forward-when-no-consumers>true</forward-when-no-consumers>                         <max-hops>1</max-hops>                         <discovery-group-ref discovery-group-name="icp-discovery-group"/>                     </cluster-connection>                 </cluster-connections>                 <grouping-handler name="icp-grouping-handler">                     <type>${grouping-handler.type}</type>                     <address>jms.queue.icp</address>                     <timeout>5000</timeout>                 </grouping-handler>                 <security-settings>                     <security-setting match="#">                         <permission type="send" roles="guest"/>                         <permission type="consume" roles="guest"/>                         <permission type="createnondurablequeue" roles="guest"/>                         <permission type="deletenondurablequeue" roles="guest"/>                     </security-setting>                 </security-settings>                 <address-settings>                     <address-setting match="#">                         <expiry-address>jms.queue.expiryqueue</expiry-address>                         <redelivery-delay>0</redelivery-delay>                         <max-delivery-attempts>1</max-delivery-attempts>                         <max-size-bytes>104857600</max-size-bytes>                         <page-size-bytes>10485760</page-size-bytes>                         <address-full-policy>page</address-full-policy>                         <message-counter-history-day-limit>10</message-counter-history-day-limit>                     </address-setting>                 </address-settings>                 <jms-connection-factories>                     <connection-factory name="invmconnectionfactory">                         <connectors>                             <connector-ref connector-name="in-vm"/>                         </connectors>                         <entries>                             <entry name="connectionfactory"/>                         </entries>                     </connection-factory>                     <connection-factory name="nettyconnectionfactory">                         <connectors>                             <connector-ref connector-name="http-connector"/>                         </connectors>                         <entries>                             <entry name="connectionfactory"/>                             <entry name="java:jboss/exported/connectionfactory"/>                         </entries>                     </connection-factory>                     <pooled-connection-factory name="hornetq-ra">                         <transaction mode="xa"/>                         <connectors>                             <connector-ref connector-name="in-vm"/>                         </connectors>                         <entries>                             <entry name="java:/jmsxa"/>                             <entry name="java:jboss/defaultjmsconnectionfactory"/>                         </entries>                     </pooled-connection-factory>                 </jms-connection-factories>                 <jms-destinations>                     <jms-queue name="expiryqueue">                         <entry name="/queue/expiryqueue"/>                     </jms-queue>                     <jms-queue name="icp.analyze">                         <entry name="/queue/icp/analyze"/>                         <entry name="java:jboss/exported/queue/icp/analyze"/>                     </jms-queue>                     .....                 </jms-destinations>             </hornetq-server> 

and here there jgroup protocol configurations:

<stack name="tcpping">                 <transport type="tcp" socket-binding="jgroups-tcp"/>                 <protocol type="tcpping">                     <property name="initial_hosts">                         machinea[7600],machineb[7600]                     </property>                     <property name="port_range">                         1                     </property>                 </protocol>                 <protocol type="merge2"/>                 <protocol type="fd_sock" socket-binding="jgroups-tcp-fd"/>                 <protocol type="fd"/>                 <protocol type="verify_suspect"/>                 <protocol type="pbcast.nakack2"/>                 <protocol type="unicast3"/>                 ......             </stack> 

log files says, hornetq clustering created seeing message when server started @ slave node.

you may have specify jgroups-channel under broad cast , discovery groups. in case like:

               <broadcast-groups>                     <broadcast-group name="icp-broadcast-group">                         <jgroups-stack>tcpping</jgroups-stack>                         <jgroups-channel>msg-channel</jgroups-channel>                         <connector-ref>                             http-connector                         </connector-ref>                     </broadcast-group>                 </broadcast-groups>                 <discovery-groups>                     <discovery-group name="icp-discovery-group">                         <jgroups-stack>tcpping</jgroups-stack>                         <jgroups-channel>msg-channel</jgroups-channel>                     </discovery-group>                 </discovery-groups>