We already posted the Junit test. It is the second attachment we put in the
bug.
- Original Message -
From: Dirk Verbeeck [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, August 03, 2004 7:48 PM
Subject: [DBCP] Bug 30426 - need
Can you check again, because I don't see it.
-- Dirk
David Rosenstark wrote:
We already posted the Junit test. It is the second attachment we put in the
bug.
- Original Message -
From: Dirk Verbeeck [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Cc: [EMAIL
Message-
From: Waldhoff, Rodney [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 01, 2002 12:25 PM
To: 'Jakarta Commons Developers List'
Subject: RE: [POOL] Bug
This could easily be done by doing a contains()
check on the collection that backs the pool before
adding the object
GenericObjectPool with this behavior.
-Original Message-
From: Waldhoff, Rodney [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 01, 2002 12:25 PM
To: 'Jakarta Commons Developers List'
Subject: RE: [POOL] Bug
This could easily be done by doing a contains()
check on the collection that backs
I've ran into another bug with Pool / DBCP.
The problem lies in GenericObjectPool's returnObject() method.
There is no check to see if the object has already been returned, it simply
adds the object back into the pool.
If the object has already been returned, then the object now appears two
that returns the object to the pool more
than once, then that code itself is buggy,
What do the rest of you think?
-Original Message-
From: James House [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 01, 2002 10:26 AM
To: [EMAIL PROTECTED]
Subject: [POOL] Bug
I've ran into another bug
