commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Locke <tlo...@tlocke.org.uk>
Subject Re: [DBCP] How to kill connection pool when app is reloaded.
Date Sat, 28 Jun 2003 13:39:59 GMT
Hi Michael,

I had this problem and I solved it by putting:

if (ds instanceof org.apache.commons.dbcp.BasicDataSource) {
    ((org.apache.commons.dbcp.BasicDataSource) ds).close();
}

in the contextDestroyed method of the context listener class of my web
app.

Cheers,

Tony.

On Thu, 26 Jun 2003, Michael Holly wrote:

> Hi
>
> I need to kill my connection pool when I reload the application.
>
> I am using Tomcat 4.1.24, Oracle 8.1.7, Win 2k, Java 1.3.1
>
> I have configured my ant script to deploy my application without
> restarting Tomcat.
>
> Server.xml has no application context information in it.
> context.xml contains the context for the application
>
> I was under the false assumption that the
> pool was an application resource and would be reset when the application
> got reloaded.   In testing yesterday I got an Oracle error about too many
> processes.  I did some digging and found that every time I redeployed
> the application the previous connection pool was staying alive.
>
> Is there a way to kill the pool?  I have a startup servlet that handles
> initiation of log4j and caching services.  I should be able to put the
> code to kill the pool in the destroy method of this servlet.
>
> Thanks
>
> Michael
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>


---------------------------------------------------------
Tony Locke                          tlocke@tlocke.org.uk.
---------------------------------------------------------


Mime
View raw message