Hello.
Seeing next mail,
http://article.gmane.org/gmane.comp.apache.db.derby.devel/6132
I understood DERBY-412 not be fixed in 10.1 branch.
//I took this is not a bug , but improvement ....
Did I misunderstand ....?
If needed, I will merge it to 10.1 branch after DERBY-496 was done.
Best regards.
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html
*/
----- Original Message -----
From: "David Van Couvering" <[EMAIL PROTECTED]>
To: "Derby Discussion" <[email protected]>
Sent: Tuesday, August 16, 2005 1:38 AM
Subject: Re: PooledConnection being closed
With the Connection.toString() that was just checked into the trunk (and
I think Tomohito backported into the 10.1 branch) you can see if the
underlying "physical" connection is the same...
David
Knut Anders Hatlen wrote:
Tony Seebregts <[EMAIL PROTECTED]> writes:
Hi,
I'm writing a connection pool manager using the
EmbeddedConnectionPoolDatasource class. The requesting object gets the
Connection object from a PooledConnection getConnection() , executes
a SQL statement and then closes the Connection.
This correctly invokes the ConnectionEventListener.close() method -
which simply marks the pooled connection as available for reused. But
when I try to resuse the connection originally supplied by the
PooledConnection getConnection() method the connection is
closed. Calling getConnection returns me a new Connection which is
(AFAIK) not the idea.
Well, the point with pooled connections is that you use
getConnection() and close() as with ordinary connections, but the
underlying physical connection is kept open. The Connection object
returned by getConnection() is a logical connection, and you cannot
use it after it is closed. If you call getConnection() again, you will
get a new logical connection, and therefore a new Connection
object. However, the new logical connection might still use the same
physical connection.
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.9/72 - Release Date: 2005/08/14
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.9/72 - Release Date: 2005/08/14
