Your networkConnector URIs look fine. Have you run the exact same test without a failover? How is the behavior different?
Are your topic subscriptions durable? So you send messages M1 with the subscriber connected and it's received (which is expected), M2 with the subscriber disconnected but before the failover and it's dropped at S1 (which may or may not be expected depending on whether your subscriber is durable), M3 is sent after the client reconnects post-failover and it's received (which is expected), and M4 is sent after M3 with no configuration changes and it gets stranded on S1 (which is unexpected). Right? What happens if you publish additional messages after M4? Are they all stuck on S1 as well? What happens if you publish additional messages after M2 but before the failover? Does that change your observed behavior? Don't worry about the producers when you're looking at JMX, they don't tell you much that's useful in my experience. It's far more useful to look at the subscriptions. For each message (M1-4), do you see enqueues and dequeues on both subscriptions (C1/2 on S1, and Client on C1/2)? Tim On Nov 19, 2015 4:46 AM, "gbrown" <gbr...@mediaocean.com> wrote: > I am using > > static:failover:(tcp://client1:61616,tcp://client2:61616)?randomize=false&maxReconnectAttempts=-1 > > A run through of the test I performed is > > Started all servers, Server1 S1, Server2 S2, Client1 C1 and Cleint2 C2. > S1 and C1 are Master and S2 and C2 are slaves > connections checked and S1 is connected to C1 > subscriber started using Failover connection to C1,C2 and connects to C1 > Message sent and processed by subscriber. > Subscriber stopped. > Add message > Can see message on C1 Server topic > C1 stopped. > Can see message on C2 Server topic > Network Connector on S1 still shows as connected to C1 server > DynamicProducer on C2 shows as connected to SRV01->CLI01 on CLI02, same as > it was before server was stopped > Add message this is received and available on the topic > Add another message and this makes it to S1 but does not get forwarded to > C1 > and is lost. > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Master-Slave-and-store-and-forward-topic-tp4704070p4704093.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
