ActiveMQ Virtual Topics do not provide any method to get the underlying queue name for MessageConsumed or MessageDelivered advisory messages
Issue
When using virtual topics, multiple physical queues get created for the different subscribers. When MessageConsumed and MessageDelivered advisories are enabled for all queues, these queues will send consumed and delivered advisories, but all of the destination information shows the virtual topic name, not the underlying queue name. This makes it impossible to know which queue the advisory came from. Either the JMSDestination should be updated, or a new header should be added to provide the ACTUAL queue name where the advisory originated from.
Environment
- Red Hat JBoss A-MQ
- 6.2.X
- Red Hat JBoss Fuse
- 6.2.X
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
