1 Reply Latest reply on Mar 27, 2018 9:13 AM by valsaraj007

    Issue with core bridge in WildFly

    valsaraj007
    valsaraj007 Mar 27, 2018 9:13 AM

      I am getting following warnings on source & target servers & message delivery to target is not working on WildFly 8.2.

      When I configured both on same server, it worked.  But not working when connected two different clusters.

       

      source warning:

      2018-03-27 07:50:14,205 WARN  [org.hornetq.core.server] (Thread-9 (HornetQ-server-HornetQServerImpl::serverUUID=6b40406d-0fda-11e8-b5b5-354f86e2e893-409747480))

      HQ222097: Address jms.queue.JMSBridgeTargetQueue does not have any bindings yet, retry #(64)

       

      Warning on target:

      2018-03-27 07:48:19,915 WARN  [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected:

      HQ119014: Did not receive data from /10.0.0.25:50432. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

       

      Here is my conf in source:

      <http-connector name="bridge-connector" socket-binding="bridge">

          <param key="http-upgrade-endpoint" value="http-acceptor"/>

      </http-connector>

      ...

      <bridges>

      <bridge name="core-bridge">

          <queue-name>jms.queue.JMSBridgeSourceQueue</queue-name>

          <forwarding-address>jms.queue.JMSBridgeTargetQueue</forwarding-address>

          <ha>false</ha>

          <use-duplicate-detection>false</use-duplicate-detection>

          <static-connectors>

      <connector-ref>

          bridge-connector

      </connector-ref>

          </static-connectors>

      </bridge>

      </bridges>

      ...

      <jms-queue name="JMSBridgeSourceQueue">

          <entry name="queue/JMSBridgeSourceQueue"/>

          <entry name="java:/jms/queue/JMSBridgeSourceQueue"/>

          <entry name="java:jboss/exported/jms/queue/JMSBridgeSourceQueue"/>

      </jms-queue>

      ...

      <socket-binding-group name="full-ha-sockets" default-interface="public">

          ...

          <outbound-socket-binding name="bridge">

      <remote-destination host="<Destination-IP>" port="8080"/>

          </outbound-socket-binding>

      </socket-binding-group>

       

      Target conf:

      <jms-queue name="JMSBridgeTargetQueue">

          <entry name="queue/JMSBridgeTargetQueue"/>

          <entry name="java:/jms/queue/JMSBridgeTargetQueue"/>

          <entry name="java:jboss/exported/jms/queue/JMSBridgeTargetQueue"/>

      </jms-queue>

      <jms-queue name="JMSBridgeTargetDLQ">

          <entry name="queue/JMSBridgeTargetDLQ"/>

          <entry name="java:/jms/queue/JMSBridgeTargetDLQ"/>

          <entry name="java:jboss/exported/jms/queue/JMSBridgeTargetDLQ"/>

      </jms-queue>