[DERBY-3258] 'Unexpected row count: expected:<0> but was:<3>' in testReleaseCompileLocks

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.7.1.4, 10.8.1.2
• Component/s: Test
• Environment: OS: Solaris Nevada snv_27a X86 64 bits - SunOS 5.11 snv_27; VJM: Sun Microsystems Inc. 1.6.0-b105
• Bug behavior facts: Regression Test Failure
• Assignee: Knut Anders Hatlen
• Reporter: Ole Solberg
• Created: 06/Dec/07 15:30
• Updated: 17/Jun/13 09:19
• Resolved: 02/Dec/10 11:48

Description

Seen in http://dbtg.thresher.com/derby/test/trunk16/jvmAll/testing/Limited/testSummary-601462.html : JDK16Jvm1.6SunOS-5.11 i86pc-i386.

There was 1 failure:
1) testReleaseCompileLocks(org.apache.derbyTesting.functionTests.tests.lang.ReleaseCompileLocksTest)junit.framework.AssertionFailedError: Unexpected row count: expected:<0> but was:<3>
at org.apache.derbyTesting.junit.JDBC.assertDrainResults(JDBC.java:596)
at org.apache.derbyTesting.junit.JDBC.assertEmpty(JDBC.java:490)
at org.apache.derbyTesting.functionTests.tests.lang.ReleaseCompileLocksTest.testReleaseCompileLocks(ReleaseCompileLocksTest.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:95)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)

Issue Links

• relates to: DERBY-5568 AssertionFailedError: Should not hold locks after commit in ResultSetMiscTest