You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/01/07 16:47:52 UTC

DO NOT REPLY [Bug 5719] New: - deadlock in StandardContext 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=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

           Summary: deadlock in StandardContext reload
           Product: Tomcat 4
           Version: 4.0 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: dsl@ts.com


If a context reload is tried using the Manager webapp, whilst also processing a
request for the context deadlock occurs.

the request serving thread is in StandardWrapper.getServletContext awaiting the
lock on the Context, whilst holding the StandardWrapper's lock (synchronized
StandardWrapper.load() method)

meanwhile, the manager's thread is in the StandardContext.reload() method,
holding the lock of the Context, and attempting to call the StandardWrapper's
synchronized  unload() method..

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>