Upon further reflection, given this behavior has existed for so long it seems like it might be prudent to wrap this change in behavior behind a property flag. Who knows how many apps that have been written that leak exceptions from their interceptors and expect that the data written in transaction is persisted regardless.

Additionally, all tests pass when removing the exception handling in org.hibernate.internal.SessionImpl#beforeTransactionCompletion

Please provide guidance on the idea of either:

1. Either remove the catch/swallow logic altogether OR
2. Provide a configuration property to allow re-throwing the exception instead of swallowing it.