Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: 17 Dec 2003 19:28:51 -0000
Message-ID: <20031217192851.28712.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 25596]  -
    application briefly unavailable when using manager to reload

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 drees@greenhydrant.com  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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org