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

Posted to dev@avalon.apache.org by bu...@apache.org on 2002/12/04 14:10:14 UTC

DO NOT REPLY [Bug 15060] - deadlock in ResourceLimitingPool

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

deadlock in ResourceLimitingPool

leo.sutic@inspireinfrastructure.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From leo.sutic@inspireinfrastructure.com  2002-12-04 13:10 -------
Harald,

could you provide a non-abbreviated stack dump?

#2  is waiting on monitor 0xd8618 (0xf1414bf0) held by #63
#63 is waiting on monitor 0xd8ab0 (0xf1414528) held by #2

#2 locked monitor 0xd8ab0 at:
    at org.apache.avalon.excalibur.pool.ResourceLimitingPool.get
       (ResourceLimitingPool.java:361)
       - locked <f1414528> (a java.lang.Object)
                    
However, I don't see where #63 locked 0xd8618 (0xf1414bf0).

Without knowing where #63 locked that monitor, I can't resolve the deadlock.

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