|
From: Leif M. <le...@ta...> - 2005-12-15 14:38:56
|
Anastasios,
The Wrapper is designed to log all console output from the JVM at
the INFO log level.
You can disable it all by setting the Wrapper's loglevel to STATUS or
higher. However,
this will mask all console output. If the JVM crashes or there is any
console output that
does not go through log4j, the Wrapper is the only way to make sure it
gets logged.
As you are using log4j, is there any reason why you don't simply
disable the console
target in your log configuration? It looks like you are logging to a
file as well.
If I am missing something, explain how you would like to see the
Wrapper behave and
as always I'll consider it.
Cheers,
Leif
Anastasios Angelidis wrote:
> Hi I'm using log4j in my applications and my console appender gets
> wrapped into the wrapper log files. Is there a way to stop this!? Thanks
>
> This is my log4j.xml config file...
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
>
> <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
>
> <appender name="console" class="org.apache.log4j.ConsoleAppender">
> <param name="target" value="System.out"/>
>
> <layout class="org.apache.log4j.PatternLayout">
> <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p
> [%c{1}] %m%n"/>
> </layout>
> </appender>
>
> <appender name="file" class="org.apache.log4j.FileAppender">
> <param name="File" value="../logs/scheduler.log"/>
>
> <layout class="org.apache.log4j.PatternLayout">
> <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p
> [%c{1}] %m%n"/>
> </layout> </appender>
>
> <root>
> <level value="info" />
> <appender-ref ref="console" />
> <appender-ref ref="file" />
> </root> </log4j:configuration>
|