JUL has been reported as 60 times slower than other implementations
because of the way they log:
http://www.infoq.com/news/2007/08/logback
Just configuring properly log4j/logback to log to System.err or
System.out should be enough to see messages properly in the AppEngine
console. In logback, it's something like this:
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%-5level %logger{0} - %msg%n
</pattern>
</encoder>
<filter class="ch.qos.logback.classic.filter.LevelFilter">
<level>ERROR</level>
<onMatch>DENY</onMatch>
<onMismatch>ACCEPT</onMismatch>
</filter>
</appender>
<appender name="STDERR" class="ch.qos.logback.core.ConsoleAppender">
<target>System.err</target>
<encoder>
<pattern>%-5level %logger{0} - %msg%n
</pattern>
</encoder>
<filter class="ch.qos.logback.classic.filter.LevelFilter">
<level>ERROR</level>
<onMatch>ACCEPT</onMatch>
<onMismatch>DENY</onMismatch>
</filter>
</appender>
<root level="DEBUG">
<appender-ref ref="STDOUT" />
<appender-ref ref="STDERR" />
</root>
Then, you can use slf4j-jcl to redirect also your commons-logging
messages.
On Oct 3, 6:14 pm, Eurig Jones <[email protected]> wrote:
> Hey,
>
> I've written a Log4j appender which passes on log4j severity levels to
> GAE's JUL framework so you can view your log4j events (or the events
> your chosen framework provides) if you need to.
>
> http://androidisland.blogspot.com/2010/10/gae-and-log4j-getting-them-...
>
> This is a quick implementation of this Appender for me and so far it
> works, but I'd love to hear some feedback about what it doesn't do (or
> doesn't do properly) as I've not used it in anger.
>
> Regards,
> Eurig Jones
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
