I have a cluster consisting of 2 pairs of master/slaves: m1/s1 and m2/s2. They use multicast://default for their networkConnectors. 1 subscriber, 1 publisher, also both using multicast urls. My subscriber is a durable subscriber. Msgs are persistent.
I am testing system robustness in the face of a master failure. I have 3 test cases, of which 2 behave as expected and 1 is problematic. My publisher connects to a master, sends a set of 10 persistent messages and exits. The subscriber (durable) receives a message and spends 1 sec simulating processing time, and waits for the next msg (auto-acknowledge). For each test case I connect the subscriber, then publish the message set, then kill a master after a few messages are received by the subscriber. When the slave comes online I expect the remaining msgs to be delivered. 1. subscribe to m2, publish to m2, kill m2. Messages are all delivered 2. subscribe to m1, publish to m2, kill m2. Messages are all delivered 3. subscribe to m1, publish to m2, kill m1. Remaining msgs are NOT DELIVERED :( In case #3, when m1 is killed I can see the subscriber reconnecting to m2. If I then connect the subscriber directly to s1 (using tcp:// url), the remaining msgs are indeed delivered. I would have expected s1 to route the remaining msgs to m1 during the test execution, but that did not happen. Any ideas? I'll followup with some log output. Thanks! -- View this message in context: http://activemq.2283324.n4.nabble.com/Cluster-Slave-not-forwarding-messages-tp4699365.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
