I wouldn't be mixing Log4j 1.1.3 and 1.2.13. Why are you using two
different versions? Pick one (the newer one) and call it a day. In
fact, download 1.2.14 just to make sure you are up to date with the
latest and greatest.
Jake
At 08:31 PM 2/13/2007, you wrote:
Hi,
Our product is havin
On Feb 15, 2007, at 10:25 AM, CHANG Shuh wrote:
Hi Rene,
Thanks for your feedback. To share the information, please keep the
feedback on the log4j users list.
The NTEventLogAppender.DLL works EXCEPT that when logged in the
EventViewer, it also records some extra messages like:
The descri
Hi Rene,
Thanks for your feedback. To share the information, please keep the feedback on
the log4j users list.
The NTEventLogAppender.DLL works EXCEPT that when logged in the EventViewer, it
also records some extra messages like:
The description for Event ID ( 4096 ) in Source ( Log4jEventLog
Glen,
I am not sure, If I really understand your question, but you "could" write
your own Custom Filter.
So, in your application, you want to set the root threshold to FATAL and
then for
certain packages lower the level to DEBUG or INFO. But for this one
package, I want to see the info and trace
It isn't hard to make one logger have more detail than the other
loggers when using the same appender but filtering out error and fatal
would probably require special filters on the appender (maybe even
custom filters).
On 2/15/07, Drinkwater, GJ (Glen) <[EMAIL PROTECTED]> wrote:
Hi
Thanks for
Hi
Thanks for the help. Also, is it possible to level filter a package
like you can do with a appender.
What I have done is to set the root threshold to FATAL and then for
certain packages lower the level to DEBUG or INFO. But for this one
package, I want to see the info and traces logged etc,
Glen,
Here is a sample which will help you understand how you can use xml config
file, basically you use the format:
In the logger section:
Here are the file contents:
Hi,
I'm a little confused about the Logger.error(msg, throwable) method.
I'm trying to log an exception at a high level, so I'm calling
logger.error("message", exception), where exception is part of a chain
of multiple exceptions.
When the log level is set to debug, the full trace of the exceptio
