Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2325

JMSBridge fails to stop after throwing an error

XMLWordPrintable

    • -
    • Hide
      Cause:
      A JMS Bridge between JBoss EAP and a TIBCO broker will throw an exception while stopping if the TIBCO broker has already been stopped/crash.
      Consequence:
      Both EAP server and the JMS bridge cannot be stopped.
      Fix:
      The JMS Bridge is performing a gracefull stop on failure.
      Result:
      EAP server and JMS bridge can be stopped if a TIBCO broker is being stopped/crash.
      Show
      Cause: A JMS Bridge between JBoss EAP and a TIBCO broker will throw an exception while stopping if the TIBCO broker has already been stopped/crash. Consequence: Both EAP server and the JMS bridge cannot be stopped. Fix: The JMS Bridge is performing a gracefull stop on failure. Result: EAP server and JMS bridge can be stopped if a TIBCO broker is being stopped/crash.
    • Hide

      To recreate the issue follow the steps:

      • Create a JMS Bridge between JBoss EAP and TIBCO EMS broker.
      • Start a JBoss EAP
      • Send a message via bridge from TIBCO to JBoss EAP
      • After message arrives in JBoss EAP kill tibia broker
      • try to run stop operation on the bridge, it should throw an exception (as above)
      • try to stop EAP server with CTRL/C - it should just hang.
      Show
      To recreate the issue follow the steps: Create a JMS Bridge between JBoss EAP and TIBCO EMS broker. Start a JBoss EAP Send a message via bridge from TIBCO to JBoss EAP After message arrives in JBoss EAP kill tibia broker try to run stop operation on the bridge, it should throw an exception (as above) try to stop EAP server with CTRL/C - it should just hang.

      JMSBridge throws an error if remote end point is stopped/terminated. After that it fails to stop

      [standalone@jess:9990 /] /subsystem=messaging-activemq/jms-bridge=pushBridge:stop()
{
    "outcome" => "failed",
    "failure-description" => "fail to stop JMS Bridge",
    "rolled-back" => true
}
[standalone@jess:9990 /]

      After that it is impossible to shutdown JBoss EAP server and it has to be killed.

        1. server.log.zip
          86 kB
        2. standalone-full.xml
          41 kB
        3. thread-dumps.zip
          54 kB

              fnigro Francesco Nigro
              rhn-support-toross Tom Ross
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: