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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2007/04/16 10:24:15 UTC

[jira] Resolved: (DERBY-2478) 'Invalid transaction state...' in jdbcapi.SetTransactionIsolationTest

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

Knut Anders Hatlen resolved DERBY-2478.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

Committed revision 529162.

> 'Invalid transaction state...' in jdbcapi.SetTransactionIsolationTest
> ---------------------------------------------------------------------
>
>                 Key: DERBY-2478
>                 URL: https://issues.apache.org/jira/browse/DERBY-2478
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure, Test
>    Affects Versions: 10.3.0.0
>         Environment: OS: SUSE Linux Enterprise Server 10 (x86_64) [Version 10 / Patchlevel 10] 64bits - Linux 2.6.16.21-0.8-smp #1 SMP Mon Jul 3 18:25:39 UTC 2006 GNU/Linux
> JVM: Sun Microsystems Inc. 1.5.0_07-b03
> OS: Red Hat Enterprise Linux AS release 4 (Nahant Update 3) 64bits - Linux 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 GNU/Linux
> JVM: Sun Microsystems Inc. 1.5.0_07-b03
>            Reporter: Ole Solberg
>         Assigned To: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: d2478.diff
>
>
> See e.g. http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/testlog/sles/520949-suitesAll_diff.txt
> 1) testIsolation(org.apache.derbyTesting.functionTests.tests.jdbcapi.SetTransactionIsolationTest)ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
> 	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> 	at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.setIsolationLevel(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedConnection.setTransactionIsolation(Unknown Source)
> 	at org.apache.derbyTesting.functionTests.tests.jdbcapi.SetTransactionIsolationTest.checkIsolationLevelNoTimeout(SetTransactionIsolationTest.java:113)
> 	at org.apache.derbyTesting.functionTests.tests.jdbcapi.SetTransactionIsolationTest.testIsolation(SetTransactionIsolationTest.java:50)
> 	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:80)
> 	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)
> <method>
> org.apache.derbyTesting.functionTests.tests.jdbcapi.SetTransactionIsolationTest
> </method>
> <signature>
> Invalid transaction state - held cursor requires same isolation level
> </signature>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.