Re: DataSource question
I am using lambdaprobe to monitor the datasource and it shows that many maxActive connections for each webapp deployed. So the total possible max connections to the database would become maxActive times number of webapps. But I would like to confirm that as I have had occasional database connectivity errors and I was suspecting if what lambdaprobe is showing isn't correct and the total possible max connections to database for all webapps combined is actually what is specified in maxActive? Anyone familiar with what I am talking about? Thanks. --- Victor Saez [EMAIL PROTECTED] wrote: I think that's the MaxActive connections on the database. Depending on how you configure the datasource it will be available for one or all webapps. The tomcat docs have a good explanation, here you got the link for tomcat 5.5. http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html Please correct me if I'm wrong, or if I missunderstood your question. Cheers! 2008/1/8, Eqbal [EMAIL PROTECTED]: I have defined my jndi DataSource for connecting to the database under the conf/context.xml file. I would like to understand what it means in terms of availability of the datasource to each of the web apps and the thing I am confused about is what is the maximum number of connections available? Is it the maxActive times number of web apps or just maxActive? Thanks. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Víctor Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DataSource question
I think that's the MaxActive connections on the database. Depending on how you configure the datasource it will be available for one or all webapps. The tomcat docs have a good explanation, here you got the link for tomcat 5.5. http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html Please correct me if I'm wrong, or if I missunderstood your question. Cheers! 2008/1/8, Eqbal [EMAIL PROTECTED]: I have defined my jndi DataSource for connecting to the database under the conf/context.xml file. I would like to understand what it means in terms of availability of the datasource to each of the web apps and the thing I am confused about is what is the maximum number of connections available? Is it the maxActive times number of web apps or just maxActive? Thanks. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Víctor
DataSource question
I have defined my jndi DataSource for connecting to the database under the conf/context.xml file. I would like to understand what it means in terms of availability of the datasource to each of the web apps and the thing I am confused about is what is the maximum number of connections available? Is it the maxActive times number of web apps or just maxActive? Thanks. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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]
RE: JNDI datasource question
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]
Re: JNDI datasource question
Thanks for your detailed explanation. In tomcat 5.0.28 I cannot find initialSize parameter. Is it something that was added later? And by idle connection, do we mean the connection that was closed in a finally block (returned to the pool)? John Tim Lucia wrote: 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JNDI datasource question
connection.close() on a pooled connection is returned to the pool, i.e., idled. Unless doing so would exceed maxIdle, in which case it would be really closed. I can't say for sure when it was added, but I can say I've used it with 5.0.28, whether or not it was documented. It's just a port / repackaging of Commons DBCP, and that has had initialSize for a long time now. Tim -Original Message- From: John Cherouvim [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 08, 2006 7:52 AM To: Tomcat Users List Subject: Re: JNDI datasource question Thanks for your detailed explanation. In tomcat 5.0.28 I cannot find initialSize parameter. Is it something that was added later? And by idle connection, do we mean the connection that was closed in a finally block (returned to the pool)? John Tim Lucia wrote: 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] - 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]
