tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <>
Subject RE: tomcat stop listen but doesn't close pool
Date Thu, 09 Dec 2004 13:23:08 GMT

You're wrong.  You need to close the pool if you want that done.  It's
not a Tomcat bug.  This has been discussed numerous times on the
tomcat-user mailing list, which is the proper venue for this type of
question, not this tomcat-dev list.

Yoav Shapira

>-----Original Message-----
>From: Filipe Lautert []
>Sent: Thursday, December 09, 2004 8:00 AM
>Subject: tomcat stop listen but doesn't close pool
>I think it's a bug, but just want to confirm it with you:
>I have an apllication that uses hibernate + jndi. it has a connection
>pool with a postgresql server. When I run the shutdown scripts of
>( or stop), tomcat stop to listen at port 8080
>but does not close the pool. The java process don't die. It stays
>but without listen at http port. Then, when i start again tomcat, it
>opens a new pool and so on, till I have an out of memory in my machine
>(because of the java processes that still alive) or I reach the maximum
>number of connections of postgresql.
>I'm wrong, or tomcat should free all resources it has and simply die
>when I stop him?
>I'm asking this because I have another tomcat that doesn't uses jndi
>when I run the shutdown scripts, the process ceases.
>To unsubscribe, e-mail:
>For additional commands, e-mail:

This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message