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

broker Health mbean doesn't seem to report error status conditions in couple cases

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Minor
    • A-MQ 7.0.0.GA
    • None
    • None
    • None

    Description

      Was hoping to force the ActiveMQ health mbean to show some error status indicators so I've tried a couple configurations to deliberately force an error condition. For example:

      1) Turn off persistence, set a low memory limit on queues (memoryLimit="512kb").

      2) Enable persistence, set a low memory limit on queues and set a low limit on storeUsage and tempStoreUsage.

      In either case I then start a second container with the "example-camel-mq" route running. I edited this route by replacing the producers message with bunches of Lorem Ipsum text. The context has a producer and consumer route. So to force an error condition, I stop the consumer route and keep an eye on messages coming into the queue. I see in the logging that producer flow control kicks in and the producer is halted. However when I check the health mbean in JMX (from hawtio) the status is shown as "good". Shouldn't this be indicating that a destination is blocked up?

      Attachments

        Activity

          People

            Unassigned Unassigned
            stlewis_2 Stan Lewis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: