Please read the docs,
The backup will only get activated when clients connect into that.
That's being changed for 2.2.
the backup server will be actived when the client has connected to the server.
i think u can try to kill the live server when u sending messages to it, then u may find the backup node actived.\
BTW, your configration files have no problems.
1 of 1 people found this helpful
Hi thanks for your response, able to see the failover happening now. But I face the same issue as https://jira.jboss.org/browse/HORNETQ-555 and http://community.jboss.org/thread/147389?start=0&tstart=0 where after the failover not able to send any messages to queue using the JCA managed connections in JBoss 5.1.0 GA.
Also I could see from JIRA https://jira.jboss.org/browse/HORNETQ-285 that this issue is fixed in 2.1.0.BETA3 and I'm using Hornetq 2.1.2 Final. So just wanted to know if JCA managed connections would work seamlessly after failover in JBoss 5.1.0 or should I wait for the fix. Thanks!
You need to keep JCA connecting to a remote node. Usually JCA is in-vm, what will activate the system right away. that's something that's being improved for 2.2.
Clebert Thanks for the info! Is there any patch or an alternate solution for now to handle this issue?