dcsimg
Fail Safe mechanism for JMS
0 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Jay_S
Posted On:   Wednesday, February 8, 2006 09:20 AM

We have an EJB which inserts data in DB ,after updating or inserting records in DB. We have to write them on the queue , for different application to pick up the changes. Please can any one suggest any mechanism by which we can insure there is no message drop ,if queue is down or some network issue. In our case Queue is Sonic queue. Can we use MBeans to take care of this ?I mean in case of exception try again sort of thing and hold that data in mean time. Or Roll back is only option ? Is there any pattern for this ? Can we have one MDB in our env which keep envoking a session bean or any java class try sending it again ? Thanks Jay    More>>

We have an EJB which inserts data in DB ,after updating or inserting records in DB. We have to write them on the queue , for different application to pick up the changes. Please can any one suggest any mechanism by which we can insure there is no message drop ,if queue is down or some network issue.
In our case Queue is Sonic queue.

Can we use MBeans to take care of this ?I mean in case of exception try again sort of thing and hold that data in mean time.

Or Roll back is only option ?

Is there any pattern for this ?
Can we have one MDB in our env which keep envoking a session bean or any java class try sending it again ?

Thanks

Jay

   <<Less
About | Sitemap | Contact