You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/03/14 22:17:48 UTC

DO NOT REPLY [Bug 18075] - Extra stop-restart after a manager deploy

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=18075>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=18075

Extra stop-restart after a manager deploy

markt@apache.org changed:

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



------- Additional Comments From markt@apache.org  2004-03-14 21:17 -------
In the circumstances you describe, I would expect to see two stops and 
restarts. The first as a result of updating the timestamp of web.xml and the 
second as a result of the redeploy through the manager app.

As I can't see anything wrong with Tomcat's behaviour in these circumstances 
(it is doing exactly what you ask it to) I am going to resolve this bug.

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