This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
We have problem on our development/deployment using jboss cluster
We deploy application on several nodes using jgroup.
We found that when one node is shutdown, our jms client in another node (which is still running) does not recognize that the other node is shutdown, so the messages will still be delivered to the shutted down node (jms client does not do fail over). That makes those message will not be properly processed (hanging processes). My friend told me that this is the common mechanism on jboss jms client. But I wonder why there are no basic mechanism in which jms client recognize that the other node is not live, and decide that those messages will be consumed by itself instead of delivering those to died node.