You're getting the ServiceUnavailableException (bottom of your stack trace) when you've killed just one node. The client proxy should have targets for Nodes A and B; you shouldn't get ServiceUnavailable unless calls to both fail. This leads me to suspect the proxy only had a target for Node A.
Recommend that on the client you enable TRACE level logging for categories org.jboss.invocation and org.jboss.ha. This should give you insight into what's going on inside the client proxy. When you kill a node via ctrl-c (or the shutdown script), stop() should be called, as ctrl-c results in a ShutdownHook running. Should be no different than calling stop() from the JMX console. If a true failure of Node A occurred (e.g. powered off the server) failover should still work. The proxy should have a target list that includes Node B and it should fail over to it. After a period of time Node B will recognize that A is dead, and will remove A from the proxy target list. A clean shutdown on A just makes this process cleaner, since the stop() method results in B being notified that A is no longer providing the service. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926994#3926994 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926994 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
