logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gulcu <...@urbanet.ch>
Subject Re: Null pointer exception with AsyncAppender
Date Thu, 11 Jan 2001 18:55:38 GMT

OK. I think I have identified the problem. You are right, in case of 
multiple close calls to AsyncAppender there will be a exception due to the 
fact that there is no longer a dispatcher. The fix is very easy:

Just add

if(closed) {

to the top of AsyncAppender.close(). I'll make a new release incorporating 
this bug fix shortly. Thanks again for the bug report. I wonder why my 
tests did not catch this... I am puzzled! Regards, Ceki

At 17:18 11.01.2001 +0000, you wrote:
>Hello there,
>I get a null pointer exception at line 105 in AsyncAppender while 
>Category.shutdown(). I am not quite shure but from my point of view it 
>looks like Hierachy.shutdown() tries to close AsyncAppender two times.
>Kind regards
>Frank-Olaf Lohmann
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

View raw message