wood burning stoves 2.0*
The moose likes EJB and other Java EE Technologies and the fly likes Remote MQ box fails, how to save messg that were supposed to be placed in Queue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Remote MQ box fails, how to save messg that were supposed to be placed in Queue" Watch "Remote MQ box fails, how to save messg that were supposed to be placed in Queue" New topic
Author

Remote MQ box fails, how to save messg that were supposed to be placed in Queue

Sam Gehouse
Ranch Hand

Joined: Jul 21, 2003
Posts: 281
I have an architectural question.

What should be the best way of handling this scenario:

Messagfes are built by client. Then those messages will be placed in remote MQ server. Remote MQ server fails (worst case scenario, even with clusreing option). What is the best way of handling a scenario like that. I can think of a few options:

1) Give error messsage to client. It may not be the best option if several messages were supposed to be placed in a short period of time.
2) Write code so that those messages are persisted in database and those messages are placed in queue when MQ server is up.

Are there any choices for installing light weight JMS server in WAS (WebSphere App Server) box that will also hold messages? In that way, even if remote MQ server dies, those messages will sit in WAS box. Channel will be set between light weight JMS server in WAS box to remote MQ box.

Any other ideas?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Remote MQ box fails, how to save messg that were supposed to be placed in Queue