[
https://issues.apache.org/jira/browse/DERBY-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-5454:
--------------------------------------
Attachment: DERBY-5454_try1.diff
I'm attaching an attempt to work around this deadlock issue by *not* doing the
select max(serial_key) at all, and instead obtaining a random number without
using jdbc.
It seems to work in as far as that with this change I do not see the deadlock
on max(serial_key) (of course, not as the code's no longer there), but
unfortunately I also see some ERROR 23505s popping up:
------from the test output redirected to nstest.out: -----------
Tester2Thread 4 inserted 1 row with id -764407904
Exception when preparing or executing insert prepared stmt
java.sql.SQLIntegrityConstraintViolationException: The statement was aborted
because it would have caused a duplicate key value in a unique or primary key
constraint or unique index identified by 'SQL120322210301700' defined on
'NSTESTTAB'.
Tester2Thread 4 dbUtil ----> During executing/preparing insert stmt in dbUtil,
exception thrown was : java.sql.SQLIntegrityConstraintViolationException: The
statement was aborted because it would have caused a duplicate key value in a
unique or primary key constraint or unique index identified by
'SQL120322210301700' defined on 'NSTESTTAB'.
java.sql.SQLIntegrityConstraintViolationException: The statement was aborted
because it would have caused a duplicate key value in a unique or primary key
constraint or unique index identified by 'SQL120322210301700' defined on
'NSTESTTAB'.
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:82)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:256)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:424)
at
org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:353)
at
org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2360)
at
org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:82)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1334)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPreparedStatement.java:1715)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(EmbedPreparedStatement.java:311)
at
org.apache.derbyTesting.system.nstest.utils.DbUtil.add_one_row(DbUtil.java:197)
at
org.apache.derbyTesting.system.nstest.tester.TesterObject.doIUDOperation(TesterObject.java:148)
at
org.apache.derbyTesting.system.nstest.tester.Tester2.startTesting(Tester2.java:109)
at org.apache.derbyTesting.system.nstest.NsTest.run(NsTest.java:555)
Caused by: java.sql.SQLException: The statement was aborted because it would
have caused a duplicate key value in a unique or primary key constraint or
unique index identified by 'SQL120322210301700' defined on 'NSTESTTAB'.
at
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:42)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:122)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:71)
... 12 more
Caused by: ERROR 23505: The statement was aborted because it would have caused
a duplicate key value in a unique or primary key constraint or unique index
identified by 'SQL120322210301700' defined on 'NSTESTTAB'.
at
org.apache.derby.iapi.error.StandardException.newException(StandardException.java:295)
at
org.apache.derby.impl.sql.execute.IndexChanger.insertAndCheckDups(IndexChanger.java:466)
at
org.apache.derby.impl.sql.execute.IndexChanger.doInsert(IndexChanger.java:383)
at
org.apache.derby.impl.sql.execute.IndexChanger.insert(IndexChanger.java:590)
at
org.apache.derby.impl.sql.execute.IndexSetChanger.insert(IndexSetChanger.java:268)
at
org.apache.derby.impl.sql.execute.RowChangerImpl.insertRow(RowChangerImpl.java:453)
at
org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(InsertResultSet.java:999)
at
org.apache.derby.impl.sql.execute.InsertResultSet.open(InsertResultSet.java:519)
at
org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(GenericPreparedStatement.java:443)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:324)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1242)
... 6 more
----------------------------------------------------------------
So I don't think this is quite right. I'll look at it some more.
I also wondered if perhaps it would be useful to have a test that has a good
chance of hitting deadlock issues and perhaps I should make the old code
available with a special test property...But decided against that because the
deadlock was not happening all the time.
> ERROR 40001 deadlock in nstest on select max(serialkey)
> -------------------------------------------------------
>
> Key: DERBY-5454
> URL: https://issues.apache.org/jira/browse/DERBY-5454
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.7.1.1, 10.8.2.2
> Reporter: Myrna van Lunteren
> Attachments: DERBY-5454_try1.diff
>
>
> nstest with 10.8.2 (both 10.8.2.1 RC2 (revision 1170221) and builds off the
> 10.8. tree at 10.8.2.2 level after backing out re DERBY-5448) show deadlock
> errors like the following:
> Caused by: ERROR 40001: A lock could not be obtained due to a deadlock, cycle
> of
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
> at
> org.apache.derbyTesting.system.nstest.utils.DbUtil.pick_one(DbUtil.java:491)
> at
> org.apache.derbyTesting.system.nstest.utils.DbUtil.delete_one_row(DbUtil.java:418)
> at
> org.apache.derbyTesting.system.nstest.tester.TesterObject.doIUDOperation(TesterObject.java:175)
> at
> org.apache.derbyTesting.system.nstest.tester.Tester2.startTesting(Tester2.java:109)
> at org.apache.derbyTesting.system.nstest.NsTest.run(NsTest.java:555)
> Caused by: java.sql.SQLException: A lock could not be obtained due to a
> deadlock, cycle of locks and waiters is:
> Lock : ROW, NSTESTTAB, (619,15)
> Waiting XID : {104564, S} , NSTEST, select max(serialkey) from nstesttab
> where serialkey > ?
> Granted XID : {104179, X}
> Lock : ROW, NSTESTTAB, (619,16)
> Waiting XID : {104179, S} , NSTEST, select max(serialkey) from nstesttab
> where serialkey > ?
> Granted XID : {104564, X}
> . The selected victim is XID : 104564.
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> Source)
> ... 14 more
> For more examples, see comments on DERBY-5448.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
