[OPENEJB-1342] Exception thrown from tx cleanup in finally block supresses cause

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.0
• Component/s: container system
• Assignee: Unassigned
• Reporter: David Jencks
• Created: 24/Aug/10 19:50
• Updated: 24/Aug/10 19:50

Description

If you have code like this in a bean-managed tx ejb:

ut.begin();
throw new RuntimeException("unexpected error");
ut.commit();

then code like this, present in all the containers, will suppress the runtime exception in favor of an uninformative message that you failed to end the transaction:

(from SingletonInstanceManager)

            try{
                //Call the chain
                interceptorStack.invoke();                
            } catch(Throwable e) {
                //RollBack Transaction
                EjbTransactionUtil.handleSystemException(transactionPolicy, e, callContext);
            }
            finally{
                EjbTransactionUtil.afterInvoke(transactionPolicy, callContext); // this throws the uninformative exception
            }

Just about every use of EjbTransactionUtil.afterInvoke suffers from this problem.