DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43683>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43683 Summary: Accessing Servlet while Reloading context gives 404 error Product: Tomcat 6 Version: 6.0.14 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If a servlet has finished it's init(ServletConfig), and is now ready to handle requests, if you tell the tomcat manager to reload the context containing that servlet (EG: w3m http://localhost:8080/manager/reload?path=/ServletRestartTest), and you access that servlet via GET or POST (EG: w3m http://localhost:8080/ServletRestartTest/ServletRestartTest) while the destroy() method on the servlet is still executing, the GET or POST request will fail with a 404 error after the destroy() method has been completed. This is always reproducible with my attached test case. I believe this may be the root cause of the issue described in #42518 which is described as an "Intermittent 404". With this test case, it is always reproducible, and not intermittent. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
