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 ------- Additional Comments From [EMAIL PROTECTED] 2003-12-17 19:28 ------- In TC 4 when I reload a context through the manager, any requests to that context don't come back until the context has been reloaded. I wonder why it's different for you? Anyway, let me post what Remy said about fixing this issue: "To solve the recurrent bugs and problems caused by reload and simplify the code, reload was replaced with the stop/start sequence. So unfortunately the side effect is that this cannot work anymore, and we need a more generic mechanism to 'wait'." I'm not sure exactly where to look but I would start with the Manager webapp and see where it ties into the container. From there, you'll have to look at how requests get processed and see if there's a way to get new requests to a context to block if a context is reloading. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
