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] New: - Reload an existing Application : KO
Date Fri, 05 Apr 2002 08:30:52 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

           Summary: Reload an existing Application : KO
           Product: Tomcat 4
           Version: 4.0.3 Final
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: zorro.desbois@wanadoo.fr


As I said in bug 7026 for tomcat 3.3x, there is a malfunction with the reload of an existing
application :

My test :
My application is already deployed.
I do some modifications on servlet(s), compile and deploy it(them).
With the manager, I reload my application AppliTest :
http://localhost:8080/manager/reload?path=/AppliTest

Result :
My application (18 threads) is well deployed (modifications are OK) 
but old native threads are still here (but inaccessible) and new native threads (18) have
been created.

So, if I repeat this operation several times,
my system is down because I can't do any fork !!!

So, at the moment and while this bug isn't resolved, I think this command (reload) must be
prohibited (or this problem indicated in the 
documentation).

Note : this problem is the same if you remove and install the application.

Thanks.
Yo

--
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