You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-user@db.apache.org by Prashanth Adhikari <sp...@hotmail.com> on 2003/06/13 03:47:55 UTC
Tuning Connection Pooling Parameters
We are using Torque with Tomcat in one of our projects. We are having some
performance issues and I am wondering if I am running into a connection
pooling issue. I recently took a Thread dump of our application while
running a 100 user load test. I found several threads waiting to lock on
Jdbc2PoolDataSource.getConnection() (called by Torque.getConnection()). I
had set "defaultMaxActive" = 50. I changed it to defaultMaxActive = -1 and
saw a performance improvement. Is this an appropriate setting to use? I am
not sure if my connection pool is getting exhausted. How can I tell at any
time what the number of active connections and idle connections are in the
pool? I tried to tried to modify Torque.getConnection() to log
Jdbc2PoolDataSource.getNumActive() and Jdbc2PoolDataSource.getNumIdle(). But
that did not seem to work, Torque.getConnection() would not even return. Any
tips on tuning connection pooling parameters or general performance tuning
with Torque will be much appreciated.
Thanks
Prashanth
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail