handle poison message in MDB 2004-12-30 - By Tong Wang
Back
Have you encountered the situation when you want to abort database
transactions but commit the JMS in Message Driven Bean (MDB) in order to
avoid poision message? If the message is bad, and some database updates
have already been done before we detected message is bad, we don't want to
commit those database changes. On the other hand, we want to commit JMS to
remove the message off the queue. That means we can't put JMS and DB in
the same global transaction. Is this the best way to handle poison
message?
Thanks
Tong
===========================================================================
To unsubscribe, send email to listserv@(protected) and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@(protected) and include in the body of the message "help".
|
|
