Thanks for the prompt reply.

The true is that we cannot live with the eaten log which leaves us clueless about the originating problem.
Our primary concern is to see the originating cause in the error log. I do not have a particular preference on how to achieve this.

Regarding the option of the configurable setRollbackOnly: if not marked as "roll back only", I suppose that the transaction manager is nevertheless going to roll back the entire transaction, or?
This could be the way to go.