"bander" wrote : | So JBM is actively changing whatever is bound as nodes go up and down etc?
Yes. But it's actually more than that. The connection factory maintains a list of nodes to failover onto and to load balance connetions across, when the cluster topology changes (a node joins or leaves) then two things happen: 1) The connection factory is rebound in JNDI with the updated list 2) An update message is sent to all the clients which already have their connection factories to make them update their internal lists. I suspect other providers might also use a similar approach. So if you re-use a CF from before the crash then it's likely it won't know about the different topology - at least you can't guarantee it since you'll have to start making nig assumptions based on the implementation details of the particular messaging system you're using. Safest thing to do is to throw it away and start again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050008#4050008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4050008 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
