The number of connections is affected by three parameters:
initialSize="10"
maxIdle="20"
maxActive="50"
also:
maxWait="5000"
initialSize="10" says make 10 connections at startup. SHOW PROCESSLIST will
reveal 10 processes in this case.
maxIdle="20" says close any idle connections in excess of 20. SHOW
PROCESSLIST will reveal 20 or fewer idle processes in this case.
maxActive="50" says to cut off incoming connections at 50. Any connection
attempt beyond 50 will wait for maxWait="5000" (5 seconds) for a free
connection before giving up.
Tim
-----Original Message-----
From: John Cherouvim [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 7:17 AM
To: users@tomcat.apache.org
Subject: JNDI datasource question
Hello
I have a JNDI Datasource pooling 10 connections on a database of my
mysql server. Why does it use only one process on the mysql server? I
have set max active to 10 connections and I am accessing the application
from different IPs at the same time. I then perform a SHOW PROCESSLIST
on mysql and I only see one process related to the datasource. On the
other hand, applications which access the database directly or using
programmatic connection polling use many processes as expected.
Could someone explain me if this is the case and why does it happen?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
