This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes JBoss/WildFly and the fly likes JMS Client Fail Over Problem? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "JMS Client Fail Over Problem?" Watch "JMS Client Fail Over Problem?" New topic

JMS Client Fail Over Problem?

istofani api

Joined: Mar 13, 2010
Posts: 1
Hi All,

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.

We are using jboss 5.1, jms 1.x.

Please help us to resolve this issue.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
subject: JMS Client Fail Over Problem?
Similar Threads
Distributed processing and workflow pattern
IBM Websphere v6 and JBoss 4x MQ Connectivity - Please Help
Processing lots of JMS messages
HornetQ stand alone client fail-over without backup servers
Why there is so hype of JMS in just to send a message? Please give some explanations..