Yes, I want to use statically defined queues exclusively. The hub is in NY and the spokes are all around the world, network outages are not rare and one of our uses for AMQ is propagating usage data to a central location. As a result, we have a long expiration on the messages (2 weeks) and want them to collect on the spokes even when the hub is not connected.
We have queues that exist just at the hub and one spoke (for messages going to the spoke) and queues that exist at all sites (for messages going to the hub). I'm using <staticallyIncludedDestinations> to ensure only the queues relevant to a particular spoke are created there. In my app, there should be no dynamically created queues. As a precaution, I would like to prevent any such queues that do get created (say, via a programming error or a bug in AMQ) from being replicated to any spokes. -- View this message in context: http://activemq.2283324.n4.nabble.com/Reply-message-not-forwarded-across-temporary-bridged-destination-tp4688578p4700169.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
