WebSphereUowTransactionManager swallows original exception when commit fails for another reason [SPR-16102] #20650
Labels
in: data
Issues in data modules (jdbc, orm, oxm, tx)
status: backported
An issue that has been backported to maintenance branches
type: bug
A general bug
Milestone
Alexander Pinske opened SPR-16102 and commented
It would be nice if the previous exception could be logged, when it is shadowed by a subsequent commit failure.
Reasoning: We are currently analysing a problem, where a JMS-Publish takes a long time and aborts after some timeout. This is the inner exception. During this time the global transaction is rolled back, which leads to an exception during commit. The behaviour is okay, but we have "lost" the actual cause of the problem.
Of course there are workaround, e.g. using a LoggingInterceptor around the transaction method, but that would log any exception (that will usually still be there after commit/rollback) not only the "shadowed" ones.
Affects: 4.3.11
Referenced from: commits 75a813a, efe943d
Backported to: 4.3.13
The text was updated successfully, but these errors were encountered: