"Expected: The request shall wait for web application reload to complete and then display the page (or error 404 in case of that bug that I was investigating). There is a loop in CoyoteAdapter that waits while context is being reloaded."
This feature is actually a bug, the server should return a response and move on. It is not a good idea to tie up an indefinite amount of requests/threads waiting for something to happen.

(In reply to Konstantin Kolinko from comment #2)
> (In reply to Remy Maucherat from comment #1)
> > It is not a good idea (...)
>
> Ack, but some people find it useful. See bug 53024 that asked for it.
This was not a feature reuqets in bug 53024. For as long as I cam remember (so back to Tomcat 4.1.x) the intended behaviour has been for the thread to wait while the context reloads.
This looks like a regression in the new static resource implementation in 8.0.x.

(In reply to Mark Thomas from comment #3)
> (In reply to Konstantin Kolinko from comment #2)
> > (In reply to Remy Maucherat from comment #1)
> > > It is not a good idea (...)
> >
> > Ack, but some people find it useful. See bug 53024 that asked for it.
>
> This was not a feature reuqets in bug 53024. For as long as I cam remember
> (so back to Tomcat 4.1.x) the intended behaviour has been for the thread to
> wait while the context reloads.
I filed the wait time issue as bug 56713.

This is ASF Bugzilla: the Apache Software Foundation bug system. In case
of problems with the functioning of ASF Bugzilla, please contact
bugzilla-admin@apache.org.
Please Note: this e-mail address is only for reporting problems
with ASF Bugzilla. Mail about any other subject will be silently
ignored.