Be interested to see if it works if you remove the dynamicallyIncludedDestinations ?
> On 10 Feb 2016, at 19:23, felixehm <felix....@cern.ch> wrote: > > Hi, > > before opening an issue, here's what we have encountered on our production > system: > > Scenario: > Given two brokers A and B in a dynamic network > (http://activemq.apache.org/networks-of-brokers.html). The bridge is > configured on broker B and works in both directions (duplex) . > > {code} > <networkConnectors> > <networkConnector uri="static://(tcp://0.0.0.0:61640)" > networkTTL="2" > messageTTL="2" > consumerTTL="2" > conduitSubscriptions="false" > decreaseNetworkConsumerPriority="false" > duplex="true" > suppressDuplicateQueueSubscriptions="false"> > > <dynamicallyIncludedDestinations> > <queue physicalName="QUEUE"/> > </dynamicallyIncludedDestinations> > </networkConnector> > </networkConnectors> > {code} > > A handler waits on broker B on a queue for incoming requests. > A client connects to A and sends a request to the queue and waits for an > answer. > > Result: > The client never receives an answer, > > Remarks: > Although his temp-queue is generated on broker B and the server answers > correctly to it, the message is not forwarded through the network. > > Question: > is this correct bahaviour ? From the docs docs > <http://activemq.apache.org/networks-of-brokers.html> this is not obvious > . > > > Thanks for clarification. > Felix > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/request-reply-broken-on-duplex-network-5-12-1-tp4707392.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
