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 2004/12/20 11:22:49 UTC
DO NOT REPLY [Bug 24159] -
Log4J can create deadlock conditions
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
meling@acm.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |meling@acm.org
Version|1.2 |1.3alpha
------- Additional Comments From meling@acm.org 2004-12-20 11:22 -------
I support any attempt to fix this bug, as I also have experienced this problem
on several occasions. SO PLEASE FIX IT.
Hein Meling
(In reply to comment #11)
> I feel a bit frustrated because I've been bitten in the ass a few times
> encountering this "contrived" problem and I haven't been taken very
> seriously pointing this out. As I have tried to explain, this is
> something that has happened before on servers at this company, and it's
> something we'd like to have fixed.
>
> If you one day turned on DEBUG and soon watched your server lock up,
> you'd be shaking your fist at whoever designed log4j. It is not just
> some annoying bug, it's also something that can result in your server
> hanging. And I'd rather have the server reboot than do that... I admit
> my test case was "contrived", but in the real world people employ
> multiple levels of indirection and the actual triggering mechanism can
> be quite convoluted. And it can lurk until one unlucky day somebody
> unknowingly turns on DEBUG.
>
> I thought in the quest for helping fix this bug we could improve
> concurrency and multi-threading. Even if you think this bug is dumb,
> wouldn't you like to improve in this area?
>
> I sent out some changes that will maintain compatibility and fix this
> issue, have you seen them?
>
> I've also talked to several people who use JBoss who have run into this
before.
--
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