I tried but was unable to re-create the error so for now no closer to finding
the cause or a solution.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
thanks for the reply, only db.data was deleted (renamed in fact).
The locks work in testing when stopping/killing/switching off the master
instance of ActiveMQ and the slave takes over and the same when going back.
I'll need to see if I can have the NFS share failing on both servers at the
same
We had a short outage on the network and once the this came back both
instances in our master / slave setup were up and connectable. Once this was
discovered when messages on queues were not browsable or able to be consumed
the instances were restarted after renaming the db.data file as other
metho
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.
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
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
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
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
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
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
Hi
When I setup 2 sets of master / slave servers and using store and forward
for topics to the second set of servers when testing the failover on the
second set the topics are in place but does not receive any new messages.
This setup works fine when using queues.
Can anyone help and provide de
11 matches
Mail list logo
