[SMXCOMP-163] Throwable is not cought in BaseLifeCycle which can result in open transactions

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 2013.02
• Component/s: servicemix-common

Environment

Everywhere

• Patch Info: Patch Available
• Assignee: Unassigned
• Reporter: Martin Landua
• Created: 30/Oct/07 15:48
• Updated: 10/Dec/12 10:11

Description

The onMessageExchange method in BaseLifeCycle only catches Exceptions. If a Throwable is thrown during processing of the Message Exchange, the transaction will not be rolled back.
As a result, the transaction keeps associated with the thread, which is returned to the thread pool. Whenever this thread is being reused, it may lead to "Already associated to a transaction" exception in any further message processing (which is not related to the actual problem in any way).

Best regards

Martin Landua

Issue Links

• is duplicated by: SMXCOMP-169 Catch throwables and not only Exceptions in BaseLifeCycle.onMessageExchange