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 24159] - Log4J can create deadlock conditions (concurrent package donation)
Date Tue, 12 Sep 2006 19:14:25 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=24159>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=24159





------- Additional Comments From srikanth_ganapavarapu@tvworks.com  2006-09-12 19:14 -------
I support any attempt to fix this bug, as I also have experienced this problem.

We're a large cable company using Tomcat for our app server needs in the back 
office for serving our content and binary streams. During our recent efforts 
to scale some of our apps to multiple markets... we are doing benchmarking of 
our servers and we're running into dead locks.

Upon investigation, we found that the root is log4j as already explained in 
this bug/thread descriptions.

We strongly support fixing this bug.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message