My understanding is that MDB's are in their own transactions. So a problem with B isn't going to roll A back. This should be the default behavior.
We have two problems we are trying to address. First, we don't need the transaction for processing message A in onMessage() to cover anything we do with message B. We also don't want any exceptions that occur in processing message B to escape and cause message A to roll back.
That part we can take care of by being careful with exception handling. The second problem is that we want message A to be processed as soon as possible, and any resources (e.g. Db) released as soon as possible, so we'd like to send message B outside of the transaction covering message A. – user677891 May 9 at 14:44 You want to separate the sending of the message or the consumption of the message?
Are you saying you want A to submit B but you don't want the submission to be part of A's transaction? If so, why? – Preston May 9 at 17:26.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.