ActiveMQ 6.2: large messages get "stuck" when using client-side composite destinations

Solution Verified - Updated -


A JMS client posts large messages (typically > 1 Mb) to a client-side composite JMS destination (for example, a destination specified by a name of the form queue_1,queue_2). Some messages are accepted by the broker, but cannot be consumed, and do not show up when browsing the destination's contents. The messages that are "stuck" are typically on the first listed destination of the composite. The problem is resolved by restarting the broker, but restarting clients does not help.


  • JBoss Fuse/ActiveMQ
    • 6.2 GA

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content