Cause: Automatic Openwire mapping of virtual topic consumer destinations to FQQN was not generating unique consumer queues. Consequence: Duplicate consumers (same name) on different addresses were not being respected. Only the first consumer would get messages. Fix: Use the full consumer destination as the queue name part of the FQQN such that the same openwire consumer-name is make uniqueue by virtue of the referenced address. Result: The same OpenWire virtual topic consumer-name, subscribed to multiple destinations gets the required messages.