[
https://issues.apache.org/jira/browse/DERBY-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171838#comment-13171838
]
Paul taylor commented on DERBY-5545:
------------------------------------
The error is not actually occurring for me but for a customer I dont seem to
have a derby.log I'll look into configuring that. I can confirm the next() does
occur after the query on the very next line, no other threads could be
consuming the resultset. I am using database pooling so if there was problem
with that I suppose it would be feasible that another thread could close the
connection that this thread had opened but that could only happen if there was
a bug in the pooling or database as my code gets the pooled connection directly
before making the query and it is private to this method.
I dont see how I can make a reproducible testcase as the problem does not
hgappen consistently the code runs perfectly for some time before the error
occurs, whihc does lead me to suspect it is linked to a reosurce problem, I
think the first step is to configure a derby.log
> 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
