commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Updated: (DBCP-11) [dbcp] stmt.getConnection() != Connection used to create the statement
Date Mon, 25 Sep 2006 05:26:53 GMT
     [ ]

Phil Steitz updated DBCP-11:

      Bugzilla Id:   (was: 36077)
    Fix Version/s: 1.3
                       (was: 1.2.2)

Changing the fix version to 1.3.  We may in fact decide on WONTFIX eventually, but I want
to hold off on that judgement until we have reworked close() systematically.

If we interpret the spec to mean that Statment.getConnection()  has to return the physical
connection that created the statement, this is in general *not* going to be equal to the connection
object that the user has a reference to and may also be open when the user's connection is

> [dbcp] stmt.getConnection() != Connection used to create the statement
> ----------------------------------------------------------------------
>                 Key: DBCP-11
>                 URL:
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2 Final
>         Environment: Operating System: other
> Platform: All
>            Reporter: Alexander Rupsch
>             Fix For: 1.3
> Hi,
> I'm not an expert in implementing connection pools or jdbc itself. But shouldn't
> the following code work?
> Connection con = pool.getConnection()
> PreparedStatement ps = con.prepareStatement()
> con.equals(ps.getConnection) // returns false!
> Ok, I don't need it to be equal, but the following also does not work:
> ps.getConnection().close()
> con.isClosed() // is false!!!
> That means, if I have a Statment and want to close its connection, I have to
> remember the conncetion. Is that the requested behavior? Because of this my pool
> is running over.
> The java.sql API says that Statment.getConnection() has to be the connection
> which created the statement.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message