ü [mailto:[EMAIL PROTECTED]
> Sent: 16 September 2004 19:43
> To: Log4NET Dev
> Subject: Re: Parsing of log files from
> FileAppender/Supporting exceptions in the PatternLayout
>
>
> Hello,
>
> In the current (log4j) code, if you are using the
> PatternLayout,
Dave,
If you're trying to parse the log file on a periodic basic to look
for errors you'd be better off using the XML Layout as that will output
XML fragments which will contain all of the data, properly formatted.
If you want to find the messages in real time instead then I'd
sugg
Hello,
In the current (log4j) code, if you are using the PatternLayout,
exceptions are handled by the appender instead of the
PatternLayout. At the time, it was assumed that the user would always
want to see the exception and it would be error prone for force the
user to specify an exception conver
We are trying to setup some automated alarming when errors are written to
our log files.
The problem we are having is that the message span multiple lines, with no
obvious beginning or end to each message.
I tried adding literals at the beginning and end of the conversion
pattern, but that didn't w
