[DBCP-11] [dbcp] stmt.getConnection() != Connection used to create the statement

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.3

Environment

Operating System: other
Platform: All

• Bugzilla Id: 36077
• Assignee: Unassigned
• Reporter: Alexander Rupsch
• Created: 08/Aug/05 20:38
• Updated: 25/Mar/08 08:11
• Resolved: 21/Jul/07 15:48

Description

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.