Craig wrote:
But I think we might be using the term recycle differently.
By recycle, do you mean if a connection has been setting in the pool
for a long time and is not allocated to an application, so we can close it
now?
No, thats pool administration. IMO its an implementation detail
The notion expressed by someone else of creating new wrappers for each
request delegating to truly pooled
connections, with the wrappers discarded when the connection is returned to
the pool would prevent refrences to
wrappers being used to access the real pooled resources.
On the other hand this
- Original Message -
From: Mario Ivankovits [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Sent: Monday, March 24, 2003 8:57 PM
Subject: Re: [DBCP] Please let us start to improve the connection pool
1) ThreadLocal
This might not help anything, or do i oversee
I use thread locals this way in web applications :
MyServlet extends SomeServlet{
...cut ...
1) This helps you to access this connection on any place within your thread,
good. But if the pool gets back the connection the thread do not loose the
instance of the pooled-connection, and so, it is
: Mario Ivankovits [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 6:24 PM
Subject: Re: [DBCP] Please let us start to improve the connection pool
The notion expressed by someone else of creating new wrappers for each
request delegating to truly
You can store connection in ThreadLocal or in request attribute.
It must be trivial to implement and you do not need workarounds.
Use SessionWrapper to detect legacy stuff and throw exeption, if some
code
tries to put connection to session.
I am sure wokarounds will not help in production.
[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 10:19 PM
Subject: Re: [DBCP] Please let us start to improve the connection pool
You can store connection in ThreadLocal or in request attribute.
It must be trivial to implement and you do not need workarounds.
Use SessionWrapper to detect legacy
On Tue, 25 Mar 2003, Juozas Baliuka wrote:
Date: Tue, 25 Mar 2003 19:14:49 +0200
From: Juozas Baliuka [EMAIL PROTECTED]
Reply-To: Jakarta Commons Developers List [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Subject: Re: [DBCP] Please let us start to improve
Hello !
There are some bug or RFE in DBCP which sould be fixed.
Some people (including me) have already posted in this list, but it seems there is no
DBCP developer anymore or he/she is very busy.
Could one of the DBCP people please comment on how and when development in DBCP could
advance.
I
Developers List [EMAIL PROTECTED]
Sent: Monday, March 24, 2003 6:34 PM
Subject: [DBCP] Please let us start to improve the connection pool
Hello !
There are some bug or RFE in DBCP which sould be fixed.
Some people (including me) have already posted in this list, but it seems
there is no DBCP
Craig,
IMHO, any application that depends on the connection pool for recovering
abandoned connections (whether or not it recycles them) is broken. Far
better is to focus your energy on avoiding all the cases where you grab a
connection from the pool but fail to return it for some reason.
Craig R. McClanahan wrote:
On Mon, 24 Mar 2003, Danny Angus wrote:
Date: Mon, 24 Mar 2003 22:28:29 -
From: Danny Angus [EMAIL PROTECTED]
Reply-To: Jakarta Commons Developers List [EMAIL PROTECTED]
To: Jakarta Commons Developers List [EMAIL PROTECTED]
Subject: RE: [DBCP] Please let us start
12 matches
Mail list logo
