logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 19684] - possible resource leak in NDC lazyRemove
Date Wed, 07 May 2003 16:41:25 GMT
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

wpitman@hotmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |



------- Additional Comments From wpitman@hotmail.com  2003-05-07 16:41 -------
The attached program illustrates conditions where by lazyRemove will fail to 
remove all dead entries, regardless of how many times it tries.

Compile and run the program as such:

java -cp log4j.jar  NDCTester 100 5 100

To create 100 threads that set NDC data but never termainte
To create 5 threads that set NDC data but terminate without calling NDC.remove()
To create 100 threads that set NDC data and do all NDC.remove()

The debug output from NDC.lazyRemove will show how many of the dead threads 
were reaped.  In this case, none of the 5 threads are removed by lazyRemove.

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


Mime
View raw message