Class A fault in rolling-file algorithm(s)

[Thomas Tuft Muller <tt...@online.no>]

Log4j users/developers

I've now tried endless combinations of parameters to the different
rollingfile appenders (CompositeRollingAppender, DailyRollingFileAppender,
RollingFileAppender) in log4j and they all make the application hang after a
rollover-attempt.

The application has a lot of threads and uses multiple appenders for a lot
of categories, some of them being async-appenders.

This (unfortunately) shows that multithreading issues are NOT solved
satisfactory in Log4j. Does anyone have any knowledge whether this is
addressed by the development team, if there exists fixes/updates etc? I
could of course fix the problem myself, unfortunately my schedule is pretty
tight for the time being.

I'm seriously considering applying another logging package, and I will
discourage use of log4j for other projects until this is solved. Dont' get
me wrong, I think log4j is an excellent logging package despite a few design
deficiencies, but no telco production system can tolerate to risk
application hangs as likely as the system today proves.

Regards,

--

Thomas












*************************************************************************
Copyright ERA Technology Ltd. 2001. (www.era.co.uk). All rights reserved. 
Confidential. No liability whatsoever is accepted for any loss or damage 
suffered as a result of accessing this message or any attachments.

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

Re: Class A fault in rolling-file algorithm(s)

[Ceki Gülcü <cg...@qos.ch>]

http://www.tuxedo.org/~esr/faqs/smart-questions.html

At 10:57 27.09.2001 +0100, you wrote:
>Log4j users/developers
>
>I've now tried endless combinations of parameters to the different
>rollingfile appenders (CompositeRollingAppender, DailyRollingFileAppender,
>RollingFileAppender) in log4j and they all make the application hang after a
>rollover-attempt.
>
>The application has a lot of threads and uses multiple appenders for a lot
>of categories, some of them being async-appenders.
>
>This (unfortunately) shows that multithreading issues are NOT solved
>satisfactory in Log4j. Does anyone have any knowledge whether this is
>addressed by the development team, if there exists fixes/updates etc? I
>could of course fix the problem myself, unfortunately my schedule is pretty
>tight for the time being.

>I'm seriously considering applying another logging package, and I will
>discourage use of log4j for other projects until this is solved. Dont' get
>me wrong, I think log4j is an excellent logging package despite a few design
>deficiencies, but no telco production system can tolerate to risk
>application hangs as likely as the system today proves.
>
>Regards,
>
>--
>
>Thomas
>
>
>
>
>
>
>
>
>
>
>
>
>*************************************************************************
>Copyright ERA Technology Ltd. 2001. (www.era.co.uk). All rights reserved. 
>Confidential. No liability whatsoever is accepted for any loss or damage 
>suffered as a result of accessing this message or any attachments.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-user-help@jakarta.apache.org

--
Ceki Gülcü - http://qos.ch

The world owes Israel a great debt for destroying Saddam's 
French built nuclear reactor in 1981 and thus preventing
nuclear blackmail in the region and perhaps beyond.
                       -- Garry Kasparov (yes, the chess player) 


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