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=5719>. 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=5719 deadlock in StandardContext reload [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-01-07 09:24 ------- sorry chaps, having installed 4.0.2 it's still everywhere (I was misreading CVS message about a different fix) Basically, there are synchronization problems in many many places during a reload. If you hit a jsp page just before reloading its context, the problem listed above can happen.. in particular the reloading thread holds many locks that the current request needs access to in order to complete, and the reloading needs the request to finish before it relinquishes these needed locks.. One particular example is (4.0.2b) when this lock up has happened is HttpProcessor: getServletContext : 1169:StandardWrapper getServletContext : 125:StandardWrapper _initialize: 128:jasper.runtime.PageContextImpl initialize: 114:jasper.runtime.PageContextImpl internalGetPageContext: 175:jasper.runtime.JspFactoryImpl getPageContext:154:jasper.runtime.JspFactoryImpl _jspServiet:45:org.apache.jsp.base1$jsp service:HttpJspBase [..skip..] doForward:431:catalina.core.ApplicationDispatcher forward:355:catalina.core.ApplicationDispatcher etc. and the manager's thread: sleep:Thread unload:1063:StandardWrapper stop:1287:StandardWrapper reload:2380:StandardContext reload:448:ManagerServlet doGet:281:ManagerServlet -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
