Re: Uncaught exception in log4j 1.2.6

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

It looks like the error was caught by log4j. The log4j:ERROR message is 
just reporting it not throwing it.

At 13:38 18.10.2002 +0000, you wrote:
>Hi, I'm not sure if this qualifies as a bug (as it was due to my own
>misconfiguration) and I can't tell if it is already logged, as Bugzilla sends
>my browser into spasms when I try to search.
>
>At http://jakarta.apache.org/log4j/docs/FAQ.html#reliable I read "If for any
>reason, log4j throws an uncaught exception, please send an email to the
>log4j-user@jakarta.apache.org mailing list." so that is what I am doing.
>
>In our app properties file, I found that
>"log4j.appender.ISO.layout=org.apache.log4j.xml.XMLLay"
>will throw an exception all the way out and crash our application (see 
>console
>output in attached file st.txt). Clearly this is because Loader attempts to
>load a class that doesn't exist (thanks to a bombed out text editor session)
>but I note this behaviour does not occur on a line such as
>"log4j.appender.AUDIT.layout=org.apache.log4j.PatternLay" -
>although log4j does complain, it doesn't stop our application.
>
>Please contact me if you require any further information etc. I have also
>attached the log4j section of our app's prop (cutdown.properties).
>
>Regards, Philip Yarra.

--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>