I believe this is currently how it is designed to work. Because the temporary queue is not part of the dynamicallyIncludedDestinations setting, the remote broker wouldn't know to forward the message for the new temporary queue. I haven't looked too closely but most likely some work would need to be done to enable temporary destinations to be compatible with dynamicallyIncludedDestinations.
On Thu, Feb 11, 2016 at 3:12 AM, felixehm <felix....@cern.ch> wrote: > Hi David, > > yes. its works if you remove this. Is this a normal behavior ? I understood > that the flag bridgeTempDestinations acts independently and request reply > works. > As the temp destination is created on the other broker I would have > expected > the correcting bridging of the message. > > cheers, > Felix > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/request-reply-broken-on-dynamic-duplex-network-5-12-1-tp4707392p4707408.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
