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

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2003/05/06 00:05:51 UTC

DO NOT REPLY [Bug 19684] - possible resource leak in NDC lazyRemove

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

possible resource leak in NDC lazyRemove

ceki@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX
            Summary|possible resource leak in   |possible resource leak in
                   |NDC lazyRemove              |NDC lazyRemove



------- Additional Comments From ceki@apache.org  2003-05-05 22:05 -------
LazyRemove gives up after 4 straigt missses, that is 4 consecutive
inspected threads in 'ht' that turn out to be alive.

The higher the proportion on dead threads in ht, the higher the chances of 
removal. lazyRemove might not catch all dead threads in one go but it will 
catch them eventually.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org