I am trying to get the required actions correct in this situation - can't hide behind a stack trace any longer.
According to the IBM book on JMS with WebSphere (Kareem Yusuf): "a TransactionRolledBackException must be thrown when a call to Session.commit results in a rollback of the current transaction".
I am having to assume that this is the same as saying "when a commit fails, the transaction gets rolled back and a TransactionRolledBackException must be thrown".
Is my assumption correct, or are things more subtle?
Pinned topic MQe: what happens when JMS Session.commit fails?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2007-10-16T15:42:22Z at 2007-10-16T15:42:22Z by Raghuram
Raghuram 110000CMNM7 Posts
Re: MQe: what happens when JMS Session.commit fails?2007-10-16T15:42:22ZThis is the accepted answer. This is the accepted answer.Hi,
JMS specification says that TransactionRolledBackException must be thrown when a call to Session.commit results in a rollback of the current transaction.
In MQ Everyplace TransactionRolledBackException is thrown if the transaction gets rolled back due to some internal error during commit.
It depends on the JMS implementation as to how the implementor handles certain scenarios.