Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-1543

Stuck msg not dispatched from broker to consumer

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Critical Critical
    • None
    • JBoss A-MQ 6.2.1
    • broker, stomp
    • Hide

      Use unit test attached.

      Show
      Use unit test attached.

      If the broker's MemoryPercentUsage is >= 70% with messages from one destination queue1, then the broker may fail to dispatch messages to consumer on another destination queue2.
      Messages appear to be stuck on queue2. They cannot be browsed and they cannot be consumed.
      If messages from queue1 get consumed and MemoryPercentUsage goes below 70%, the messages on queue2 will eventually be dispatched to consumer.
      However it could be that there is no consumer for queue1 for a longer time and then prevents other consumers on other destinations to retrieve any messages.

              gtully@redhat.com Gary Tully
              rhn-support-tmielke Torsten Mielke
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: