tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 7759] - Reload an existing Application : KO
Date Mon, 08 Apr 2002 08:38:11 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7759>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7759

Reload an existing Application : KO

zorro.desbois@wanadoo.fr changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From zorro.desbois@wanadoo.fr  2002-04-08 08:38 -------
I think there is a misunderstanding with my problem :
It is not my application which fork new threads but Tomcat.

My application is deployed with a file web.xml in which I precise, for each
servlet, the attribute <load-on-startup>.
My application is composed with 18 servlets.
So, when I start Tomcat, 18 threads are created by Tomcat (one thread per
servlet).
I touch one servlet code, re-compile, re-deploy my application and then reload
via the manager.

18 new threads are created BY TOMCAT (corresponding to the servlets) but the 18
old threads are still active.

So, my application doesn't fork anything but TOMCAT FORK NEW THREADS for
servlets.
So it is the responsability of the container to cleanup its resources.

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


Mime
View raw message