You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (Updated) (JIRA)" <ji...@apache.org> on 2012/04/07 01:28:26 UTC
[jira] [Updated] (DERBY-5454) ERROR 40001 deadlock in nstest on
select max(serialkey)
[ 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_try2.diff
Attaching a second patch which just does not attempt to do a select max(serial_key).
I found the original code confusing and the comments appeared contrary to what was happening.
A deadlock was happening regularly but seemed not the point, and so was only complicating the test.
I modified the code to just generate a random number and insert that.
If no one has any objections I'll commit this over the weekend and backport it to 10.8.
> 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, DERBY-5454_try2.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