In our application we want to use non-persistent messages but benefit from failover (ie master-slave configuration using kahadb).
I did some experiments today and contrary to my expectations it looks like activemq 5.9.0 supports this scenario. Huzzah! I had a producer and consumer connecting to a topic and stopped the master server in mid-execution. The producer switched over to the slave broker, as did the consumer. My questions for you kind folks: 1. Are my findings valid? That is, does activemq 5.9.0 support master/slave failover with non-persistent messages? 2. We are leaning towards kahadb as the most stable and performant solution for failover; is this true? 3. The default 10 second lock check is going to be too slow for our application... I'd like to make this number as small as possible. Any guidance? Is a sub-second value too much to ask for? Thanks for any help! -- View this message in context: http://activemq.2283324.n4.nabble.com/Failover-and-non-persistent-messages-tp4676862.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
