-
Bug
-
Resolution: Done
-
Major
-
4.0.0.Final, 4.1.0.Final, 4.2.0.ALPHA1
-
None
-
None
If CallInterceptor.handleDefault(...) is called with a RemoteTxInvocationContext, and if command invocation throws an exception, the catch clause ends up hiding this with an IllegalStateException.
The culprit is RemoteTxInvocationContext.isValidRunningTx(), which internally calls RemoteTxInvocationContext.getRunningTransaction(), which always throws an ISE.
If this method would instead return null, RemoteTxInvocationContext.isValidRunningTx() will return false, and all is well, and the genuine exception can propagate properly.
- relates to
-
ISPN-639 IllegalStateException when tx context is propagated
- Closed