-
Enhancement
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
We should track the stack trace of the first, or of each, caller of setRollbackOnly(), and if the transaction ultimately throws RollbackException or similar, we can add the stack trace as a cause. If multiple calls are done, then the latest should be the cause and the earlier should show up as suppressed exceptions.
- is blocked by
-
WFLY-10174 Upgrade WildFly Transaction Client to 1.1.2.Final
- Closed
- is incorporated by
-
WFTC-45 Track stack trace of calls to setRollbackOnly()
- Resolved