Single connections create bottlenecks and slow down throughput when the
site get's busy. DBCP allows for multiple managed connections for
faster performance. Plus it can take care of when connections die and
create new ones automatically.
There are shades of grey as well. I have one solution that made use of
commons-pool (the pool component of DBCP). The app manages a pool of
workers, each with a set of prepared statements ready to go. It boosted
performance on the app a lot over the original single connection design.
--David
Ran wrote:
Hi all,
How does DBCP compare to application managed, single connection which
stays
open to share ?
Thanks,
ran
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
