You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have experienced that BTM masks some SQLException’s if database errors occurs.
Further investigations of the source code has shown that is only occurs in LrcXAResource, and in all occurrences, every time around auto commit handling.
Are there an explicit reason why the original cause is masked away? The cause could contain any reason from internal DB errors to lost connection.
Snippet try { connection.setAutoCommit(true); } catch (SQLException ex) { throw new BitronixXAException("cannot reset autocommit on non-XA connection", XAException.XAER_RMERR); }
The text was updated successfully, but these errors were encountered:
We have experienced that BTM masks some SQLException’s if database errors occurs.
Further investigations of the source code has shown that is only occurs in LrcXAResource, and in all occurrences, every time around auto commit handling.
Are there an explicit reason why the original cause is masked away? The cause could contain any reason from internal DB errors to lost connection.
Snippet
try {
connection.setAutoCommit(true);
} catch (SQLException ex) {
throw new BitronixXAException("cannot reset autocommit on non-XA connection", XAException.XAER_RMERR);
}
The text was updated successfully, but these errors were encountered: