tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "neal" <nealcab...@yahoo.com>
Subject RE: DBCP - connection pool exhausted
Date Mon, 28 Oct 2002 04:20:14 GMT
Thanks for the tips!

You are right.  I may not have been releasing the connection objects
properly. I was presuming that a JSP would release it when the page was
complete.  Guess not???

Is removeAbandon a method of one of the DBCP classes, or one of the JDBC
(sql) classes? Which class does it belong to?  I am not familiar with this
method.

Also, is nullifying the resultsets when they're no longer needed a known
necessity with connection pooling or is this just a 'better safe than sorry'
recommendation? I always thought that the connection itself was the only
thing that needed releasing.  Please tell me if that's incorrect.

Thanks.
Neal

-----Original Message-----
From: p200002 [mailto:p200002@hotmail.com]
Sent: Sunday, October 27, 2002 6:56 PM
To: Tomcat Users List
Subject: Re: DBCP - connection pool exhausted


1. make sure that you have closed all the resultset, stmt and connections
after use.
2. set removeabandon....to recover those unclosed resource.
3. make sure you are not reading at the end of the result set.

----- Original Message -----
From: "neal" <nealcabage@yahoo.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Sunday, October 27, 2002 10:34 PM
Subject: DBCP - connection pool exhausted


> Does anyone know what causes this error when using DBCP for database
> connection pooling?
>
> "DBCP could not obtain an idle db connection, pool exhausted"
>
> Currently, I have maxActive users set to 100, and currently there are only
2
> people using the site (still in testing).  Here's my server.xml config
> details for DBCP (I replaced the sensitive data with 'xxxxx').  Please let
> me know if anyone knows why I might be having this error.
>
> Thanks!
> Neal
>
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> <Context path="" docBase="" debug="10">
>   <Resource name="jdbc/xxxxx" auth="Container" type="javax.sql.DataSource"
> />
>   <ResourceParams name="jdbc/xxxxx">
>     <parameter>
>       <name>factory</name>
>       <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
>     </parameter>
>     <parameter>
>       <name>maxActive</name>
>       <value>100</value>
>     </parameter>
>     <parameter>
>       <name>maxIdle</name>
>       <value>30000</value>
>     </parameter>
>     <parameter>
>       <name>maxWait</name>
>       <value>100</value>
>     </parameter>
>     <parameter>
>      <name>username</name>
>      <value>xxxxx</value>
>     </parameter>
>     <parameter>
>      <name>password</name>
>      <value>xxxxx</value>
>     </parameter>
>     <parameter>
>        <name>driverClassName</name>
>        <value>com.mysql.jdbc.Driver</value>
>     </parameter>
>     <parameter>
>       <name>url</name>
>       <value>jdbc:mysql:///xxxxx</value>
>     </parameter>
>   </ResourceParams>
>
> </Context>
>
>
> --
> To unsubscribe, e-mail:
<mailto:tomcat-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:tomcat-user-help@jakarta.apache.org>
>

--
To unsubscribe, e-mail:
<mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:tomcat-user-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message