ActiveMQ broker becomes unresponsive with very large enqueue/dequeue counts on ActiveMQ.DLQ

Solution In Progress - Updated -

Issue

After a period of time, the ActiveMQ message broker becomes decreasingly responsive to clients, and may eventually accept no new messages, despite memory and storage thresholds being sufficient for expected usage.

At the same time, inspection of the dead-letter destination, typically ActiveMQ.DLQ, shows large numbers of messages enqueued and dequeued -- perhaps billions -- even though the total number of messages on the destination may be low or zero.

Environment

  • Red Hat JBoss ActiveMQ
    • 6.1.0 GA
  • Red Hat JBoss Fuse
    • 6.1.0 GA

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.