[Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-05-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-05-07 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #8 from Mark Thomas --- I can recreate this with the provided test case. The 404 response is not the expected behaviour. Tomcat should pause the request until the application finishes reloading and then server. -- You are rece

DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-04-10 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #7 from Ferenc Lutischan 2012-04-10 18:12:03 UTC --- > This isn't a bug: it's how Tomcat works. Why would your undeployed context > still be able to successfully serve requests? Tomcat 6 doesn't send 404 when context is reload

DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-04-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #6 from Karl Penney 2012-04-09 18:07:46 UTC --- It shouldn't reject requests while the context is being reloaded. The StandardContextValve waits for the reload to complete, but by that point it can be too late since the request

DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-04-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #5 from Christopher Schultz 2012-04-09 16:28:16 UTC --- (In reply to comment #4) > The problem seems to be that the wrappers (servlets) are unregistered from the > context as part of the stop process. If a request comes in befo

DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-04-06 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #4 from Karl Penney 2012-04-07 00:59:09 UTC --- The problem seems to be that the wrappers (servlets) are unregistered from the context as part of the stop process. If a request comes in before the context is started again, then

DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-04-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #3 from Ferenc Lutischan 2012-04-04 11:40:27 UTC --- Test case: - Unzip the downloaded Tomcat 7.0.26 from tomcat.apache.org site - Edit the unzipped dir/conf/tomcat-users.xml. Add the following line: - Unzip the attached "T

DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-04-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 --- Comment #2 from Ferenc Lutischan 2012-04-04 11:30:55 UTC --- Created attachment 28542 --> https://issues.apache.org/bugzilla/attachment.cgi?id=28542 Test application Test application -- Configure bugmail: https://issues.apache.org

DO NOT REPLY [Bug 53024] Accessing Servlet while Reloading context gives 404 error

2012-04-03 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=53024 Christopher Schultz changed: What|Removed |Added OS/Version||All --- Comment #1 from Chri