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 "Andreas Korneliussen (JIRA)" <de...@db.apache.org> on 2006/01/02 17:35:03 UTC
[jira] Created: (DERBY-787) cursor closed as a sideeffect of closing another cursor with the same name on another connection
cursor closed as a sideeffect of closing another cursor with the same name on another connection
------------------------------------------------------------------------------------------------
Key: DERBY-787
URL: http://issues.apache.org/jira/browse/DERBY-787
Project: Derby
Type: Bug
Components: SQL
Environment: Java 1.4
Reporter: Andreas Korneliussen
Fix For: 10.1.2.1
I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
in ResultSet.updateRow().
The test does the following:
1. set up a connection, and run a query which selects one tuple
2. update the tuple using updateXXX and updateRow
3. rollback the transaction and close the connection
Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
The problem has been reproduced on forward only, updatable resultsets.
Workaround:
It does not seem to fail if I
a, set another cursorname on the statement object,
b, use the same query string.
I will attach the program to reproduce the problem. Below is the output:
~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
1,1,19,Tuple 1
2,2,21,Tuple 2
ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=comments#action_12371420 ]
Andreas Korneliussen commented on DERBY-787:
--------------------------------------------
I think I have found what caused this issue.
The "UPDATE WHERE CURRENT OF SQLCUR0" is prepared and compiled and produces an Activation (generated code) which can be reused by other connections, since the compiled code is cached.
The generated code keeps a cursor name and it will during execution look up a CursorActivation based on the cursor name.
The CursorActivation is the code for the cursor (the select statement).
During execution, the class CurrentOfResultSet has a method called getCursor(). It finds the CursorActivation for the LanguageConnectionContext, however it has a check that the prepared statement object for the CursorActivation is the same as it was whem first compiling "UPDATE WHERE ..". This will only be the case if it was the same statement string which produced the cursors.
Here is some debug of the LanguageConnectionContext.lookupCursorActivation(..)
1st connection:
(XID = 562), (SESSIONID = 1), (DATABASE = cis), (DRDAID = null), [BaseActivation: Source: select * from t1 where a=1 FOR UPDATE, ObjectName =582f8014-010a-21d6-1c29-00000016c7a0, BaseActivation: Source: UPDATE "APP"."T1" SET "A"=?,"B"=? WHERE CURRENT OF "SQLCUR0", ObjectName =6839c016-010a-21d6-1c29-00000016c7a0]
2nd connection:
(XID = 566), (SESSIONID = 2), (DATABASE = cis), (DRDAID = null), [BaseActivation: Source: select * from t1 where a=2 FOR UPDATE, ObjectName =e03f4017-010a-21d6-1c29-00000016c7a0, BaseActivation: Source: UPDATE "APP"."T1" SET "A"=?,"B"=? WHERE CURRENT OF "SQLCUR0", ObjectName =6839c016-010a-21d6-1c29-00000016c7a0]
As you can see, the Connections do not share the CursorActivation code.
Fixing this issue could be to remove the check that the prepared statement objectname for the cursor is the same.
If anyone knows a case were this would be incorrect, please let me know.
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Bernt M. Johnsen resolved DERBY-787:
------------------------------------
Resolution: Fixed
Committed revision 391559.
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java, DERBY-787.diff, DERBY-787.stat, derbyall_report.txt
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=comments#action_12362001 ]
Mamta A. Satoor commented on DERBY-787:
---------------------------------------
I think Andreas (as part of derby-231 "FOR UPDATE" required for updatable result set to work) enhanced the information used during cache lookup to differentiate between readonly select statement against updatable select statement. Something like that might need to be done to associate a statement with cursor to the right connection.
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-787) cursor closed as a sideeffect of closing
another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andreas Korneliussen closed DERBY-787:
--------------------------------------
Resolution: Fixed
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1, 10.2.0.0
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Fix For: 10.2.0.0
> Attachments: CursorIsClosedIssue.java, DERBY-787.diff, DERBY-787.stat, derbyall_report.txt
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-787) cursor closed as a sideeffect of closing another cursor with the same name on another connection
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=comments#action_12361952 ]
Dag H. Wanvik commented on DERBY-787:
-------------------------------------
What is is happening here is that the updateRow operation generates
identical "UPDATE .. WHERE CURRENT OF SQLCUR0" statements for the two
connections.
The statement cache contains a compiled plan (from connection one),
when connection two tries to do the updateRow, resulting in using the
wrong plan (which refers to the result set of the first connection,
which happens to be closed when connection two tries to do its
updateRow).
I have checked the ISO wording about cursors, and from what I can
understand, cursor names should be scoped locally to a connection, but
I cannot find any logic in the compiler statement caching to handle
this.
A partial solution might possibly be to generate cursor names which
are unique per connection for the updatable cursor case, but that
would seem to be just side-stepping the issue. If the user sets the
cursor name explicitly (JDBC Statement#setCursorName) to the same name
in several connections, the scenario would still fail.
I guess one could make the compiler *not* cache statements involving
cursors (similar to what is done for statements referring temporary
tables), but that would force recompilation at every execution of an
{update,delete}Row, which is undesirable as well.
A possibly better approach would be to have the compiler distinguish
the two similar looking statements when it compares them during the
cache lookup operation, by extending the recorded information so that
a comparison would only match - when the statement contains a cursor -
if the cached plan refers a cursor from the current connection.
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andreas Korneliussen updated DERBY-787:
---------------------------------------
Fix Version: 10.2.0.0
Version: 10.2.0.0
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1, 10.2.0.0
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Fix For: 10.2.0.0
> Attachments: CursorIsClosedIssue.java, DERBY-787.diff, DERBY-787.stat, derbyall_report.txt
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andrew McIntyre updated DERBY-787:
----------------------------------
Other Info: (was: [Patch available])
Derby Info: [Patch Available]
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java, DERBY-787.diff, DERBY-787.stat, derbyall_report.txt
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andreas Korneliussen updated DERBY-787:
---------------------------------------
Attachment: DERBY-787.diff
DERBY-787.stat
derbyall_report.txt
Attaching the patch for this issue. Removing the check that "UPDATE .. WHERE CURRENT OF .." only can execute against the cursors which comes from the same prepared statement as it was origianlly compiled with.
Testing: Removed the workaround in the SURTests which were added due to this bug. All SURTest will then use the same cursor name, and we will hit this bug if only the testing changes are applied. With the patch, everything works fine. Also the repro program successfully runs with this patch.
Ran derbyall, and got two failures. In one of the tests, the network server threw a java.net.SocketException: Connection reset exception when shutting down. The other failure is a known regression. These failures are not relevant for this patch.
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java, DERBY-787.diff, DERBY-787.stat, derbyall_report.txt
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-787) cursor closed as a sideeffect of closing another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andreas Korneliussen updated DERBY-787:
---------------------------------------
Attachment: CursorIsClosedIssue.java
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andreas Korneliussen reassigned DERBY-787:
------------------------------------------
Assign To: Andreas Korneliussen
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andreas Korneliussen updated DERBY-787:
---------------------------------------
Other Info: [Patch available]
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java, DERBY-787.diff, DERBY-787.stat, derbyall_report.txt
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Reopened: (DERBY-787) cursor closed as a sideeffect of
closing another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andreas Korneliussen reopened DERBY-787:
----------------------------------------
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1, 10.2.0.0
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Fix For: 10.2.0.0
> Attachments: CursorIsClosedIssue.java, DERBY-787.diff, DERBY-787.stat, derbyall_report.txt
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-787) cursor closed as a sideeffect of closing another cursor with the same name on another connection
Posted by "Andreas Korneliussen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-787?page=all ]
Andreas Korneliussen updated DERBY-787:
---------------------------------------
Fix Version: (was: 10.1.2.1)
Version: 10.1.2.1
> cursor closed as a sideeffect of closing another cursor with the same name on another connection
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-787
> URL: http://issues.apache.org/jira/browse/DERBY-787
> Project: Derby
> Type: Bug
> Components: SQL
> Versions: 10.1.2.1
> Environment: Java 1.4
> Reporter: Andreas Korneliussen
> Attachments: CursorIsClosedIssue.java
>
> I was writing some tests for the Scrollable updatable ResultSet feature, and found some tests failing with
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> in ResultSet.updateRow().
> The test does the following:
> 1. set up a connection, and run a query which selects one tuple
> 2. update the tuple using updateXXX and updateRow
> 3. rollback the transaction and close the connection
> Then, repeat the process, however this time use a different string in the query. This time updateRow() may fail with the error above.
> The problem has been reproduced on forward only, updatable resultsets.
> Workaround:
> It does not seem to fail if I
> a, set another cursorname on the statement object,
> b, use the same query string.
> I will attach the program to reproduce the problem. Below is the output:
> ~:/<3>db-derby-10.1.2.1-bin/lib> java -cp /home/ak136785/devel/derbytesting/derbytest/build/classes/:derby.jar derbytest.CursorIsClosedIssue
> 1,1,19,Tuple 1
> 2,2,21,Tuple 2
> ERROR XCL07: Cursor 'SQLCUR0' is closed. Verify that autocommit is OFF.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.getCursor(Unknown Source)
> at org.apache.derby.impl.sql.execute.CurrentOfResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.NormalizeResultSet.openCore(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.setup(Unknown Source)
> at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.updateRow(Unknown Source)
> at derbytest.CursorIsClosedIssue.runTest(CursorIsClosedIssue.java:80)
> at derbytest.CursorIsClosedIssue.main(CursorIsClosedIssue.java:103)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira