Konstantin Orlov created IGNITE-24325:
-----------------------------------------
Summary: Jdbc. Fix flaky
ItJdbcMultiStatementSelfTest.testAutoCommitFalseTxControlStatementsNotSupported
Key: IGNITE-24325
URL: https://issues.apache.org/jira/browse/IGNITE-24325
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Konstantin Orlov
After IGNITE-23792, test
{{ItJdbcMultiStatementSelfTest.testAutoCommitFalseTxControlStatementsNotSupported}}
started to fail from time to time to time with
{code}
java.sql.SQLException: Transaction is already finished
[id=0194a836-ff39-0000-34e8-030800000001, state=ABORTED].
at
org.apache.ignite.internal.jdbc.proto.IgniteQueryErrorCode.createJdbcSqlException(IgniteQueryErrorCode.java:57)
at
org.apache.ignite.internal.jdbc.JdbcStatement.execute0(JdbcStatement.java:161)
at
org.apache.ignite.internal.jdbc.JdbcStatement.executeQuery(JdbcStatement.java:115)
at
org.apache.ignite.jdbc.ItJdbcMultiStatementSelfTest.testAutoCommitFalseTxControlStatementsNotSupported(ItJdbcMultiStatementSelfTest.java:435)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
{code}
The reason is that {{JdbcConnectionContext}} doesn't check the status of
current transaction, which in fact may be rolled back due to error in previous
statement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
