Well, thanks to Torsten, I was able to get onto a path that worked. My solution actually ended out being two producers writing the same message to two separate queues (lets say queueLocal and queueRemote). One queue is bridged to the remote server, where there is a consumer MBD listening on queueRemote. A local MDB consuming queueLocal. That way each queue has only a single consumer.
Both MDB are identical, but listening to different queues. This creates the desired effect of the "same" message being consumer locally then remotely. I suspect there is a more elegant solution to this problem, but this works. The biggest downside so far is basically having to different versions of my consumer application, so the MDB can be listening on one queue locally, and a different one remotely (MDB are not very dynamic). The solution to that might be trying to not use MDB. -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-Bridge-trying-to-copy-all-messages-to-remote-server-tp4659769p4659906.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
