tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Johnson <>
Subject RE: When does tomcat call the garbage collector?
Date Sat, 27 Sep 2003 22:10:10 GMT

In that case, you'd want to write a class that implements
javax.servlet.ServletContextListener to manually shutdown your pool
classes when the webapp is stopped. This is handy for webapp reloads
during development, too.

- Mike Johnson

On Fri, 2003-09-26 at 12:34, Bruce W. Marriner wrote:
> 	For some reason I figured when tomcat shutdown, along with the JVM
> <-- it would finalize any open classes.  And with that action it would
> close the open connections.  Yes the open connections will die after a
> set value, some x odd hours.  It is rather easy to control the number
> of pooled connection and close them while tomcat is running.  But it's
> the shutdown part I'm concerned about.  But when 200 some odd users
> are using an app it's rather slow to run everyone off a single DB
> connection :).  Is there some way to tell JVM to finalize all open
> classes at exit?  Some command-line argument or com call, or
> something...
> -----Original Message-----
> From: Filip Hanik []
> Sent: Friday, September 26, 2003 2:15 PM
> To: Tomcat Users List
> Subject: Re: When does tomcat call the garbage collector?
> it is your own responsibility to close connections from a pool.
> Tomcat doesn't do garbage collection, the Java VM does.
> Also, if you kill your VM and the connections are still open on the AS400
> box, tough luck, (I would imagine they should timeout shortly) that is out
> of reach from the VM/Tomcat side, best thing you can do is to not keep a
> pool of open connections, because if the VM crashes or gets killed, there
> will be no one closing them from the client
> Filip
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message