[OWB-1111] firing a during-transaction event fails if the tx is already rolled back or not active

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.8, 1.6.2
• Fix Version/s: 1.6.3
• Component/s: Java EE Integration
• Assignee: Mark Struberg
• Reporter: Mark Struberg
• Created: 15/Jan/16 11:34
• Updated: 11/Mar/16 22:12
• Resolved: 24/Jan/16 20:05

Description

Consider you have an observer method like

public void clearCacheAfterTx(@Observes(during=TransactionPhase.AFTER_COMPLETION) ClearAfterTx payload) {...}

and you fire the event

clearCacheEvent.fire(new ClearCacheEvent());

In this case firing the event currently blows up if the underlying transaction is already closed or rolled back. This happens because the transaction spec states that you cannot register a tx Synchronisation in certain states:
https://docs.oracle.com/javaee/6/api/javax/transaction/Transaction.html#registerSynchronization%28javax.transaction.Synchronization%29