I had the same issue and unfortunely it seems that it is back .
My test applications are not equals of you, as I am doing some tests about
failover and H.A. using 2 simple applications.
But, the bottom line  is : when master goes down, you (and me) want that the
slave start working properly AND ,both Producer and COnsumer continue work.
But , doing my tests looks like that the Consumer just stops and finishs
when Master goes down . 
I had opened another thread here, where I mention that I realized the issue
. I mentioned there that (or I realized)  that the "start method invocation
" should be just after the connection creation :
connection = factory.createConnection();
 connection.start();

I did the change in the code. And I recall that it was working . But, for
some "kind of catasthrofe" to me, it is not working and , now, I do not know
if I did some change in the configuration (xml change)  or something or
anything else.
Going crazy with failover configuration .(and little bit dissapointed as
failover is very important for any enterprise messaging setup and I am
realizing it is not simple and it is not easy as ApacheMQ site states ) 
regards 

--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Activemq-Clustering-and-failover-tp4326849p4352501.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to