Re: Master/Slave and store and forward topic

2015-12-08 Thread Tim Bain
Glad to hear it, and I wish I'd caught that sooner. Tim On Dec 7, 2015 9:20 AM, "gbrown" wrote: > Thank you this has resolved my problem. > > Appreciate you looking into this. > > Gary > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Master-Slave-and-store-and-f

Re: Master/Slave and store and forward topic

2015-12-07 Thread gbrown
Thank you this has resolved my problem. Appreciate you looking into this. Gary -- View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-and-store-and-forward-topic-tp4704070p4704663.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Master/Slave and store and forward topic

2015-12-05 Thread Tim Bain
Your networkConnectors need to have maxReconnectAttempts=0 if you're using failover. This allows the bridge to be rebuilt (which reinitializes the subscriptions properly) when a reconnect occurs; with a non-zero setting, the failover transport eats the fact of the reconnect and the bridge ends up

Re: Master/Slave and store and forward topic

2015-11-24 Thread gbrown
This is my nc entry, same entry on server1 and server2 I am using kahadb with a shared file system, nfs4. Gary -- View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-and-store-and-forward-topic-tp4704070p4704240.html Sent from the ActiveMQ - User mailing list a

Re: Master/Slave and store and forward topic

2015-11-24 Thread artnaseef
Can you clarify the network configuration? It would help to see the network connector settings for every individual broker. Something like the following format would be great: Server1 - static:failover:(...) - static:failover:(...) Server2 - static:failover:(...) - static:failover:(...) ... A

Re: Master/Slave and store and forward topic

2015-11-21 Thread gbrown
Yes the dequeue and enqueue counts on the S1 server change as expected. I have not found any clues in the activemq.log, these are my current settings in the log4j.properties log4j.logger.org.apache.activemq.spring=DEBUG log4j.logger.org.apache.activemq.web.handler=WARN log4j.logger.org.springfram

Re: Master/Slave and store and forward topic

2015-11-20 Thread Tim Bain
OK, that's good info, and thank you for the version number. Am I right to assume that if there were any errors or other unexpected output in the logs on any of your brokers, you'd have mentioned them by now? What about enqueue and dequeue counts for subscriptions on S1? Do you see all enqueues t

Re: Master/Slave and store and forward topic

2015-11-19 Thread gbrown
Also in this test we are only testing with one subscriber. we would have more once we get it working properly. -- View this message in context: http://activemq.2283324.n4.nabble.com/Master-Slave-and-store-and-forward-topic-tp4704070p4704100.html Sent from the ActiveMQ - User mailing list archiv

Re: Master/Slave and store and forward topic

2015-11-19 Thread gbrown
Looking in HAWTIO on the C2 server the subscriber is called Durable(client1_subscriber1) the Enqueue counter only increased by 1 after failover which could be consumed. After this no more messages make to this subscriber and the counter does not increase. Hope that is the right counter. As I reali

Re: Master/Slave and store and forward topic

2015-11-19 Thread Tim Bain
My question about enqueues and dequeues was about those counts on each *subscription*, and it wasn't clear from your answer whether that's what you're describing or whether you're describing counts on the topic. On Nov 19, 2015 7:13 AM, "gbrown" wrote: > Subscription is durable. > > When the subs

Re: Master/Slave and store and forward topic

2015-11-19 Thread gbrown
Subscription is durable. When the subscription is stopped and before we failover the messages make it to C1 and are consumed when the subscription is started. So M1 with sub started is consumed and M2, M3, M+ with sub down and then restarted are consumed before failover. With Failover M4 is rece

Re: Master/Slave and store and forward topic

2015-11-19 Thread Tim Bain
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 be

Re: Master/Slave and store and forward topic

2015-11-19 Thread gbrown
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

Re: Master/Slave and store and forward topic

2015-11-18 Thread Tim Bain
Do you see a subscription from the new master of the second pair on the master of the first pair? Also, how are your networkConnectors configured? Did you remember to use either masterslave: or static:failover: transports? Tim On Nov 18, 2015 1:52 PM, "gbrown" wrote: > Hi > > When I setup 2 se