Return-Path: 
 <tomcat-dev-return-8349-qmlist-jakarta-archive-tomcat-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org
Received: (qmail 51741 invoked from network); 8 Apr 2002 08:38:04 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 8 Apr 2002 08:38:04 -0000
Received: (qmail 5644 invoked by uid 97); 8 Apr 2002 08:38:12 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org
Received: (qmail 5626 invoked by uid 97); 8 Apr 2002 08:38:11 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 5613 invoked by uid 50); 8 Apr 2002 08:38:11 -0000
Date: 8 Apr 2002 08:38:11 -0000
Message-ID: <20020408083811.5612.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 7759]  -
    Reload an existing Application : KO
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

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>