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

Handle Messages with Missing Routing Information in SF Queue / Cluster Bridge

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • clustering
    • None
    • 2
    • False
    • None
    • False
    • Hide

      Messages must be manually removed from the SF queue to recover the bridge.

      1. Stop the cluster bridge if needed
      2. Remove the offending message from the top of the queue / move to another queue
      3. Restart the cluster brige

      Show
      Messages must be manually removed from the SF queue to recover the bridge. 1. Stop the cluster bridge if needed 2. Remove the offending message from the top of the queue / move to another queue 3. Restart the cluster brige

      Currently, if a poison message missing queue information ends up in the SF queue, the broker logs an error, like:

      AMQ222110: no queue IDs defined...

      but the message remains in the queue, with the result that the bridge continuously reconnects, encounters the failure, then evicts the bridge consumer.

        1. ClusterNodeIdChangeTest.java
          6 kB
          Gary Tully

              gaohoward Howard Gao
              rhn-support-dhawkins Duane Hawkins
              Mikhail Krutov Mikhail Krutov
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: