commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hope, Matthew" <>
Subject RE: Pool project still active
Date Fri, 25 Jul 2003 09:22:37 GMT

> -----Original Message-----
> From: Chad La Joie [] 
> Sent: 25 July 2003 01:07
> To: Jakarta Commons Users List
> Subject: Re: Pool project still active
> So my suggestion, if you want an unlimited number of 
> connections is to 
> set the max allowable connections to Integer.MAX_VALUE, which 
> is really 
> the max possible connections you can have open anyways.

I would point out that your DBA may not be too happy about this - every
RDBMS has limits to the number of connections it can have open (and it's a
lot lower than Inteeger.MAX_VALUE). Often it is better to set a limit for
you application lower than this to allow a little headroom for admin users
to get in if there is a problem, I would suggest asking your DBA how many
concurrent connections to the DB would be reasonable...

Obviously if this is for a performance test suite you may actually want to
push it as far as possible to see what those limits are... but I would
discourage any user from actually setting the value to this in a non test


* I don't think you meant this but I thought it was a point worth making in
case it was misinterpreted by others as being a good thing to do
The information transmitted herewith is sensitive information intended only
for use by the individual or entity to which it is addressed. If the reader
of this message is not the intended recipient, you are hereby notified that
any review, retransmission, dissemination, distribution, copying or other
use of, or taking of any action in reliance upon this information is
strictly prohibited. If you have received this communication in error,
please contact the sender and delete the material from your computer.

View raw message