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=25596>. 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=25596 application briefly unavailable when using manager to reload [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From [EMAIL PROTECTED] 2003-12-22 07:50 ------- I looked at some of the code and just wanted to ask you guys if there is any problem with replacing the ContainerBase.invoke implementation with something along the lines of. public final void invoke(Request request, Response response) throws IOException, ServletException { while ( getPaused () ) { synchronized(this){ wait(1000);} } pipeline.invoke(request, response); } According to the StandardContext implementation the reload method call setPaused(true ) setPaused(false) during the process of reloading. Please let me know of the side effects for this solution that you might anticipate so that I might be aware of it. Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
