Testing failover on dispatcher/java-broker cluster

2016-09-14 Thread Antoine Chevin
Hello Qpid community, I’m testing the resilience of a dispatcher/broker infrastructure and I noticed the following behavior: I run a test with one JMS client connected to a dispatcher, which is connected to a broker. 1) Using JMS I establish a connection to the dispatcher and create a

Re: Testing failover on dispatcher/java-broker cluster

2016-09-14 Thread Antoine Chevin
Two details I did not mention in my previous mail: - I use the same JMS connection/session to recreate a MessageProducer - I noticed that the dispatcher reconnects correctly to the broker and the autolinks are 'active'. This is the dispatcher config that I used for this test: router { id: rou

Re: Testing failover on dispatcher/java-broker cluster

2016-09-14 Thread Ted Ross
Hi Antoine, In the broker traces, I see connection shutdown after the transfer but before you shut down the broker. Do you know what is happening there? What was the disposition of the delivery? -Ted On 09/14/2016 09:12 AM, Antoine Chevin wrote: Hello Qpid community, I’m testing the res

Re: Connecting to the router

2016-09-14 Thread Andrew Stitcher
On Tue, 2016-09-13 at 16:33 -0700, Justin Ross wrote: > Some potentially interesting things. > > ## Components > > python-qpid-proton-0.13.1-1.fc24.x86_64 > python-qpid-messaging-0.34-9.fc24.x86_64 (qpid*_*messaging) > qpid-dispatch-router-0.6.1-2.fc24.x86_64 > > ## Listener config > > listener