commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tauzell, Dave" <>
Subject RE: Production use of Connection Pooling
Date Mon, 05 May 2003 17:05:10 GMT
The DBCP code is a bit different from the Commons Pool, right?  

I read the paper and some things do apply to the commons pool (like the
wrapper requirement) but I wouldn't say I've noticed any performance
problems with my use of the Commons Pool yet.


-----Original Message-----
From: Timko, Cheryl A. [] 
Sent: Monday, May 05, 2003 11:57 AM
To: 'Jakarta Commons Users List'
Subject: RE: Production use of Connection Pooling

Have you encountered any performance issues?

We performed load testing on both the DBCP and our "custom" database
connection pool.  What we found is that when 300 concurrent users are
accessing the DBCP, the response time average is 8 sec.  When we ran the
same test using our "custom" pool, the average response time is 2 sec. 

In both tests, we were testing the connection when borrowing it from the

Thanks in advance for your help.

- Cheryl

-----Original Message-----
From: Frank Lawlor [] 
Sent: Friday, May 02, 2003 1:34 PM
Subject: Production use of Connection Pooling

I just went through a project where we looked at using the commons
pooling in a production application.


We found a number of serious problems with its use.  Anyone considering
production use of the commons pooling or any pooling product should be
aware of these issues.


We also documented some programming practices for using pooled


To see these look in the White Papers section of

for Jakarta_Pooling.doc and Proper_JDBC.doc


  -- Frank


Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA)
that may be confidential, proprietary copyrighted and/or legally
privileged, and is intended solely for the use of the individual or
entity named on this message.  If you are not the intended recipient,
and have received this message in error, please immediately return this
by e-mail and then delete it.


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

View raw message