Mirrored Queues
Features > Destination Features > Mirrored Queues
Mirrored Queues
Queues provide an excellent reliable and high performance load balancing mechanism. Each message placed on a queue can only be successfully processed by a single consumer. This is a good thing! 
. However sometimes you want to monitor what messages flow between the producers and consumers on a queue.
To do this you can use Virtual Destinations to setup a virtual Queue which forwards the message to multiple physical queues. However enabling this for every single queue in your system can be painful.
So to make it easy to monitor queues, we have added a feature we call Mirrored Queues. Mirrored Queues are kinda like a zero-configuration Wire Tap on all of your queues inside your Message Broker.
Example
For example imagine we have a number of producers sending to queue Foo.Bar and consumers consuming from queue Foo.Bar and we want to monitor or view activity.
If you enable Mirrored Queues then by default you can subscribe to the topic VirtualTopic.Mirror.Foo.Bar and receive all the messages that are sent to the queue Foo.Bar. Since its a topic as many consumers can subscribe to this topic as are required.
If you want you can use this feature with Virtual Topics; so that you can define a logical consumer; say called A. Then you can subscribe to the queue Consumer.A.VirtualTopic.Mirror.Foo.Bar to receive all the messages sent to queue Foo.Bar for the consumer A. You can then run multiple instances of this consumer who can then load balance among each other.
This combination of Mirrored Queues and Virtual Destinations can be extremely useful for monitoring transaction flows; for example with Business Activity Monitoring (BAM).
How Mirrored Queues work
When enabled, mirrored queues causes every message sent to a queue to also be sent to a topic of a similar name; so that folks who are interested in watching message exchanges on a queue can consume from the mirrored queue topic.
When coupled with Virtual Topics on this topic as described in the above example, you can actually end up creating new queues which are mirrors of a given queue dynamically at runtime!
Enabling Mirrored Queues
By default Mirrored Queues is disabled; as enabling it will cause a virtual topic to be created for each queue you use.
To enable Mirrored Queues, set the useMirroredQueues property on BrokerService or add the following inside the
<destinationInterceptors>
<mirroredQueue copyMessage = "true" postfix=".qmirror" prefix=""/>
</destinationInterceptors>
This would make a topic named “*.qmirror” for each queue on your Broker.
