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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/11/17 18:41:44 UTC
[jira] Resolved: (DERBY-3806) java.sql.SQLException: Cannot close a
connection while a transaction is still active thrown on Connection.close
[ https://issues.apache.org/jira/browse/DERBY-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-3806.
-----------------------------------
Resolution: Invalid
Resolving as invalid. User indicated that it was because he left result sets open.
> java.sql.SQLException: Cannot close a connection while a transaction is still active thrown on Connection.close
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3806
> URL: https://issues.apache.org/jira/browse/DERBY-3806
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Environment: All operating systems
> Reporter: Nathan Boy
>
> java.sql.SQLException: Cannot close a connection while a transaction is still active is being thrown when I am closing a transaction after committing. This does not happen for all transactions, and so far I have been unable to figure out why it happens for this particular one. The steps the program is taking are as follows:
> 1 - Get a connection to the embedded database
> 2 - Set autocommit to false
> 3 - Execute a number of statements and prepared statements
> 4 - Commit
> 5 - Close all prepared statements
> 6 - Close the connection
> The exception is being thrown when the actual Connection.close() method is invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.