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 2003/01/24 21:21:03 UTC

DO NOT REPLY [Bug 16406] New: - Deadlock in StandardWrapper/Context ?

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=16406>.
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=16406

Deadlock in StandardWrapper/Context ?

           Summary: Deadlock in StandardWrapper/Context ?
           Product: Tomcat 4
           Version: 4.0.4 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: gurumlore@mailexcite.com


I have an webapp A that tries to contact another webapp B during init(). Webapp
B happens to be hosted in the same container. 
Is that a no-no ? 

The connecting app A hangs and never gets a response back; and when in this
state any further attempts to contact B also hang.

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