something stops working) are really the only
good options I can think of unless logging is just a "nice to have" and
isn't a critical subsystem.
Eric
Jacob Kjome wrote:
On Mon, 14 Sep 2009 08:55:14 +0100
Michael Erskine wrote:
From: Jacob Kjome [mailto:h...@visi.com]
Subject
unless logging is just a "nice to have" and
isn't a critical subsystem.
Eric
Jacob Kjome wrote:
On Mon, 14 Sep 2009 08:55:14 +0100
Michael Erskine wrote:
From: Jacob Kjome [mailto:h...@visi.com]
Subject: Re: Verifying initialization
have you tried using?.
-Dlog4j.debug=tru
cob Kjome [mailto:h...@visi.com]
>>> Subject: Re: Verifying initialization
>>> have you tried using?.
>>> -Dlog4j.debug=true
>>
>> I think what is being discussed here (correct me if I'm wrong) is the
>>_unattended_ programmatic verification of
On Mon, 14 Sep 2009 08:55:14 +0100
Michael Erskine wrote:
From: Jacob Kjome [mailto:h...@visi.com]
Subject: Re: Verifying initialization
have you tried using?.
-Dlog4j.debug=true
I think what is being discussed here (correct me if I'm wrong) is the
_unattended_ program
> From: Jacob Kjome [mailto:h...@visi.com]
> Subject: Re: Verifying initialization
> have you tried using?.
> -Dlog4j.debug=true
I think what is being discussed here (correct me if I'm wrong) is the
_unattended_ programmatic verification of initialisation rather than
have you tried using?.
-Dlog4j.debug=true
Jake
On Fri, 11 Sep 2009 10:46:53 -0700 (PDT)
ecmcn wrote:
OK, thanks guys. I'm using a couple of custom appenders and so can at least
check that those loaded ok.
I agree with the "fail gracefully" approach, but not so much with "fail
silent
OK, thanks guys. I'm using a couple of custom appenders and so can at least
check that those loaded ok.
I agree with the "fail gracefully" approach, but not so much with "fail
silently".
Eric
--
View this message in context:
http://www.nabble.com/Verifying-initialization-tp25392804p25405474.h
I don't think you're going to find anything in log4j proper which can help you
find out this type of information.
I believe that one of the major design goals for log4j was for the framework to
fail gracefully, and not have logging errors cause application errors - not to
prevent an application
> From: ecmcn [mailto:eric.mcne...@gmail.com]
> Subject: Verifying initialization
> What are some common techniques for verifying Log4J startup and
> initialization completed successfully?
>
> For a specific example, if DOMConfigurator can't parse my XML config file
> I'll get errors to stdout but
