And try to use
removeAbandoned="true" logAbandoned="true" removeAbandonedTimeout="120"
to track which connections were not properly closed (see
http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html)
Regards
Jan
Steve Kirk wrote:
how many concurrent requests are you handling? you have configured
<name>maxActive</name>
<value>100</value>
so as soon as 100 concurrent conns are reached, you will exhaust the pool.
If you do not have as many as 100 concurrent conns, then it is likely that
your servlet calls are not returning conns to the pool after they have
finished using them. Make sure that your servlets' doPost() and doGet()
methods include a call to the Connection#close() method before they return,
whether or not an error occurred. This returns connections to the pool, for
use by other threads using the pool. The best place to call the close()
method is in a finally() block.
-----Original Message-----
From: KUMAR, NANDA [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday 26 October 2005 16:13
To: users@tomcat.apache.org
Subject: Error: Cannot get a connection, pool exhausted
Frequently we were getting "Cannot get a connection, pool
exhausted" error
on production. I know in our application, we are closing the
connection
after each connection. Here is our context.xml parameters and
values. We set
maxActive connection to 100. Please let me know what we are
doing wrong or
if you need more information.
<?xml version='1.0' encoding='utf-8'?>
<Context displayName="TestWeb" docBase="test" path="/test"
workDir="work\Catalina\localhost\test">
<Resource name="jdbc/TestDataSource" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/TestDataSource">
<parameter>
<name>url</name>
<value>jdbc:oracle:thin:@test.com:1521:test</value>
</parameter>
<parameter>
<name>password</name>
<value>test123</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>10000</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>oracle.jdbc.driver.OracleDriver</value>
</parameter>
<parameter>
<name>username</name>
<value>test</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>30</value>
</parameter>
</ResourceParams>
</Context>
Thanks
Kumar
--------------------------------------------------------------
-------------------------------------------
This e-mail message may contain privileged and/or
confidential information, and is intended to be received only
by persons entitled to receive such information. If you have
received this e-mail in error, please notify the sender
immediately. Please delete it and all attachments from any
servers, hard drives or any other media. Other use of this
e-mail by you is strictly prohibited.
All e-mails and attachments sent and received are subject to
monitoring, reading and archival by Monsanto. The recipient
of this e-mail is solely responsible for checking for the
presence of "Viruses" or other "Malware". Monsanto accepts no
liability for any damage caused by any such code transmitted
by or accompanying this e-mail or any attachment.
--------------------------------------------------------------
-------------------------------------------
---------------------------------------------------------------------
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]
