commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <>
Subject [jira] Commented: (DBCP-329) SQLException: Already closed.
Date Tue, 30 Mar 2010 04:22:27 GMT


Paul Benedict commented on DBCP-329:

Phil, you piqued my interest. Let's say a production database crashes during the day (my company
is familiar with it!), which naturally kills all connections. The crash happened in-between
the last good operation but before the close(). Do you intend an exception to propagate to
the caller who is now finished with the database? Just seems like an unnecessary hassle. Any
further thoughts?

> SQLException: Already closed.
> -----------------------------
>                 Key: DBCP-329
>                 URL:
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.4
>         Environment: MySQL
>            Reporter: Hontvari Jozsef
> After upgrading to 1.4 I see such exceptions logged:
> java.sql.SQLException: Already closed.
> 	at org.apache.commons.dbcp.PoolableConnection.close(
> 	at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(
> 	...
> This should never happen. According to the Connection.close() javadoc: 
> "Calling the method close on a Connection object that is already closed is a no-op."
> Moreover, I am pretty sure that our code does not close the connection twice. But because
the close() is called in a finally block, it is possible that this exception hides another
exception. Unfortunately I cannot reproduce it, even though it occurs regularly.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message