OK, things are a bit clearer. Don't know the full answer yet but we're getting there.
"jkressin" wrote : | But the most intersting question for me is: Even if the (Master-)node lost some viewchanges, why does it suddenly undeploy the (HA-)queues and (HA-)topics? They are undeployed because when view 203 came in, 65.20.43.211 was no longer the first node in the view, 62.50.43.211 was. All HASingleton services (currently, we're looking to change this) run on the first member in the view on which they are deployed. If a node that is currently the singleton master for the service discovers its no longer that first node, it will stop providing the service. "jkressin" wrote : And why is the failover not happening, no other node is starting to deploy the queues and topics instead. I cannot explain how this is possible and also found no information in the docs or in the forums on this issue. This is the key question. 65.20.43.211 should have taken over as the HA-JMS server and deployed the queues and topics. Is there anything interesting in the 65.20.43.211 logs that could shed light on why it didn't? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954498#3954498 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954498 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
