Spring Integrity violation exceptions are being hidden for EXASOL.

I have discovered that when java.sql.Connection#setAutoCommit set to 'false' PK/FK violations ignored. After debugging I noticed that Exasol does these checks on java.sql.Statement#close rather than on java.sql.PreparedStatement#executeUpdate. Checked JdbcUtils class I found that it is ignoring all "on close" exceptions however this specific case should be handled because otherwise transactions management won't work with EXASOL.

Comment From: pivotal-issuemaster

@YLesko Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

Comment From: pivotal-issuemaster

@YLesko Thank you for signing the Contributor License Agreement!

Comment From: snicoll

Thanks for the PR but we can't hardcode a vendor-specific handling like that. If you're still experiencing this issue, please create a new issue with a small sample and we can look what, if any, we can do in the core framework about it.