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=33589>. 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=33589 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |major Component|Catalina |Webapps:Manager OS/Version|All |Linux Platform|All |PC ------- Additional Comments From [EMAIL PROTECTED] 2005-02-16 10:11 ------- There are 2 sorts of stop Context : 1- When you want to stop a context because it has possibly a problem, the actual stop context is good because you want to force the stop as quickly as possible and you don't want to wait for anything. 2- When you to stop the context because you want to install a new WAR, I'd like my clients don't know about it. So, I'd want a "stop light" (with waiting for running threads). The service is not interrupted because, while I install my new WAR, mod_jk balance the requests on the other(s) tomcat. And when I am ready, I start my context and "stop light" the others. The 2nd case is not resolved with a reload, because, when I install my new WAR, (in default localhost with unpackWARs="true") my context is not the new One. So I need a stop... -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
