db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5568) AssertionFailedError: Should not hold locks after commit in ResultSetMiscTest
Date Thu, 05 Jan 2012 17:24:40 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-5568:
--------------------------------------

    Attachment: d5568-1a.diff

I suspect that this failure has the same root cause as DERBY-3258; that post-commit work happens
when the lock table is checked, and extra locks show up because of it.

The attached patch makes ResultSetMiscTest wait for the post-commit work to complete before
it checks the contents of the lock table. This is the same fix as the one applied to ReleaseCompileLocksTest
in DERBY-3258.
                
> AssertionFailedError: Should not hold locks after commit in ResultSetMiscTest
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-5568
>                 URL: https://issues.apache.org/jira/browse/DERBY-5568
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.8.2.2
>         Environment: Solaris 11 on x86 hardware
> java version "1.7.0_04-ea"
> Java(TM) SE Runtime Environment (build 1.7.0_04-ea-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 23.0-b09, mixed mode)
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d5568-1a.diff
>
>
> Saw this failure when running the 10.8.2.2 regression tests on Java 7u4-b06:
> 1) testBug4810(org.apache.derbyTesting.functionTests.tests.jdbcapi.ResultSetMiscTest)junit.framework.AssertionFailedError:
Should not hold locks after commit
>         at org.apache.derbyTesting.functionTests.tests.jdbcapi.ResultSetMiscTest.checkLocksForAutoCommitSelect(ResultSetMiscTest.java:695)
>         at org.apache.derbyTesting.functionTests.tests.jdbcapi.ResultSetMiscTest.testBug4810(ResultSetMiscTest.java:478)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>         at junit.extensions.TestSetup.run(TestSetup.java:25)
>         at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>         at junit.extensions.TestSetup.run(TestSetup.java:25)
>         at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)

--
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

        

Mime
View raw message