• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JMS Client Fail Over Problem?

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.

Thanks,
Istofani
reply
    Bookmark Topic Watch Topic
  • New Topic