[
https://issues.apache.org/jira/browse/DERBY-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173362#comment-13173362
]
Dag H. Wanvik commented on DERBY-5545:
--------------------------------------
If a query is successful, the result set should be open and the call to next
should return true or false, depending on whether there query generated any
data. You stack trace indicated the result set is not open. I don't see how
this could happen. Possibilities:
a) somehow, the result set gets closed. This could be due to some code between
the successful query and the call to next in the current thread, or some other
thread got hold of the result set. You state this is not the case.
b) some unknown bug in Derby makes it return a result set in the closed state
without throwing an SQLException.
Without more data, I cannot say what the issue is. Can you show the code
fragment of the query and the "next" call?
> 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
