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

Mamta A. Satoor updated DERBY-5662:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_9  (was: )
    
> nstest causes ERROR X0X03: Invalid transaction state - held cursor requires 
> same isolation level
> ------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5662
>                 URL: https://issues.apache.org/jira/browse/DERBY-5662
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.0.0
>            Reporter: Kristian Waagan
>            Priority: Minor
>              Labels: derby_triage10_9
>
> When running the nstest the test logs and, depending on the settings, 
> derby.log contains many instances of this error:
> ERROR X0X03: Invalid transaction state - held cursor requires same isolation 
> level
> Stack:
> ERROR X0X03: Invalid transaction state - held cursor requires same isolation 
> level
>       at 
> org.apache.derby.iapi.error.StandardException.newException(StandardException.java:268)
>       at 
> org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.setIsolationLevel(GenericLanguageConnectionContext.java:2906)
>       at 
> org.apache.derby.impl.jdbc.EmbedConnection.setTransactionIsolation(EmbedConnection.java:2199)
>       at 
> org.apache.derbyTesting.system.nstest.utils.DbUtil.update_one_row(DbUtil.java:374)
>       at 
> org.apache.derbyTesting.system.nstest.tester.TesterObject.doIUDOperation(TesterObject.java:162)
>       at 
> org.apache.derbyTesting.system.nstest.tester.Tester1.startTesting(Tester1.java:113)
>       at org.apache.derbyTesting.system.nstest.NsTest.run(NsTest.java:551)
> I've also seen the same stack with Tester2.
> To reduce verbosity in the logs, it would be good to avoid triggering this 
> error.

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

        

Reply via email to