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 "Dag H. Wanvik (Commented) (JIRA)" <ji...@apache.org> on 2011/12/16 22:16:31 UTC
[jira] [Commented] (DERBY-5545) Exception ResultSet not open.
Operation 'next' not permitted. Verify that autocommit is OFF exception
occuring on rs.next() after long run.
[ https://issues.apache.org/jira/browse/DERBY-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171198#comment-13171198 ]
Dag H. Wanvik commented on DERBY-5545:
--------------------------------------
Do you see anything indicating a memory problem, say, in derby.log? If you are certain the next() happens immediately after a successful query, could there be other threads consuming/closing the result set? If you could make a repro it would be helpful.
> Exception ResultSet not open. Operation 'next' not permitted. Verify that autocommit is OFF exception occuring on rs.next() after long run.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5545
> URL: https://issues.apache.org/jira/browse/DERBY-5545
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.8.2.2
> Environment: OSX 10.6
> Reporter: Paul taylor
>
> Im seeing this error occur after loading alot of data into the Database. I can confirm that autocommit is set to off, and that it occurs on calling rs.next() immediatlely after running a query and assigning to resultset rs. The cdoe is called many times (250,000) and usually works, then suddenly it starts going wrong, I also using c3po database pooling. Im wondering if the problem is linked to memory consumption although I have no OutOfMemoryError occurring
>
> Java.sql.SQLException: ResultSet not open. Operation 'next' not permitted. Verify that autocommit is OFF.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.newSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.checkIfClosed(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.checkExecIfClosed(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
> at com.mchange.v2.c3p0.impl.NewProxyResultSet.next(NewProxyResultSet.java:2859)
--
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