Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9372

The core bridge service runs on an infinite loop when the target server instance is not reachable

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • TBD EAP 5
    • EAP_EWP 5.1.2
    • HornetQ

    • JBoss-EAP-5.1.2, HornetQ-2.2.10-B2+JBPAPP-8396

    • Hide
      • Prepare two JBoss-EAP-5.1.2 instances with JBPAPP-8396 patch
      • On the source server, please configure the following
      • Configure a connector
        <connector name="netty-bridgeConnector">
        <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>
        <param key="host" value="XXX.XXX.XXX.XXX"/>
        <param key="port" value="5446"/>
        </connector>
      • Configure the source destination
        <queue name="jms.queue.bridgeSource">
        <address>jms.queue.bridgeSource</address>
        </queue>
      • Configure the core bridge as follows
        <bridges>
        <bridge name="bridge-sample">
        <queue-name>jms.queue.bridgeSource</queue-name>
        <forwarding-address>jms.queue.bridgeTarget</forwarding-address>
        <retry-interval>5000</retry-interval>
        <retry-interval-multiplier>1.0</retry-interval-multiplier>
        <reconnect-attempts>-1</reconnect-attempts>
        <static-connectors>
        <connector-ref>netty-bridgeConnector</connector-ref>
        </static-connectors>
        </bridge>
        </bridges>
      • Start the "source" server where the bridge has been configured at
      • Please do not start the "target" server instance
      • Start the JMX console and try to stop the bridge service by calling stop()
      • The server is unable to stop the bridge service and it throws "Timed out waiting to stop" WARN message
      Show
      Prepare two JBoss-EAP-5.1.2 instances with JBPAPP-8396 patch On the source server, please configure the following Configure a connector <connector name="netty-bridgeConnector"> <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class> <param key="host" value="XXX.XXX.XXX.XXX"/> <param key="port" value="5446"/> </connector> Configure the source destination <queue name="jms.queue.bridgeSource"> <address>jms.queue.bridgeSource</address> </queue> Configure the core bridge as follows <bridges> <bridge name="bridge-sample"> <queue-name>jms.queue.bridgeSource</queue-name> <forwarding-address>jms.queue.bridgeTarget</forwarding-address> <retry-interval>5000</retry-interval> <retry-interval-multiplier>1.0</retry-interval-multiplier> <reconnect-attempts>-1</reconnect-attempts> <static-connectors> <connector-ref>netty-bridgeConnector</connector-ref> </static-connectors> </bridge> </bridges> Start the "source" server where the bridge has been configured at Please do not start the "target" server instance Start the JMX console and try to stop the bridge service by calling stop() The server is unable to stop the bridge service and it throws "Timed out waiting to stop" WARN message
    • Compatibility/Configuration
    • NEW

      The core bridge service runs on an infinite loop when the target server instance is not reachable.

      At this stage, the core bridge service does not respond to the stop() command when invoked via the JMX Console.

              csuconic@redhat.com Clebert Suconic
              rhn-support-tywickra Tyronne Wickramarathne
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: