logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject Re: Socket appender causes system freeze...!
Date Thu, 20 Jun 2002 08:31:03 GMT
11.3. Deadlocks occurring after the introduction of log statements
into an application.

On numerous occasions users have complained about deadlocks after
introducing log statements into their code. However, without exception
the bug was always in the application code not in log4j. This is not
to say that log4j is totally bug-free but you need to provide some
proof before accusing log4j and jumping to conclusions.  In the
typical case, the introduction of logging statements reveals existing
concurrency problems because log statements add delay which may change
the order of execution among threads, causing an existing concurrency
problem to come to surface.

At 12:22 20.06.2002 +0600, you wrote:
>i'm using socket appender to write log messages to a remote location, in a
>mission critical application.
>whenever the traffic is heavy (at least i think that's the reason), the
>application get stuck and never recovers.
>but if work fine if i remove the socket appender.
>has anybody noticed such a thing?
>is it a bug thats already been fixed in later versions.
>pls help


To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

View raw message