Jboss日志包装我的log4j消息

Question

I've got a bizarre problem with Log4J under JBoss 7.1.0CR1b (we're just porting to JBoss now, no idea if this happens in older versions). The log lines from my EAR are all being wrapped in an INFO level. So, for example, my log line looks like this:

13:09:14,684 INFO  ERROR  CRK TEST! 

The actual log line is using a log4j Logger.error( "CRK TEST!" ). Where the heck is the extra "INFO" coming from? My guess is the logger message is being wrapped by JBoss's logger somehow since this doesn't happen with pure JBoss container messages, such as:

13:08:07,177 INFO  [org.jboss.msc] JBoss MSC version 1.0.1.GA

I've fiddled with various log4j settings and trying to walk through the debugger, but coming up blank on why this is happening. Any ideas?

Answer 1

I think log4j is writing to stdout which JBoss STDIO takes and outputs as INFO messages to the JBoss Log Manager.

There is a plan to have per deployment logging which could fix this issue, unless your appender is always writing to stdout.

So your best solution would be to look at the appender you're using and see where it's writing. If it's writing to stdout it will always appear like that.

Answer 2

I would guess that your logger is somehow connected to System.out and/or System.err and that someone (perhaps JBoss, perhaps some other EAR/WAR/...) installs a custom OutputStream which wraps everything printed to it into another logger message. Perhaps the missing '[...]' part indicates, that the root logger has been used.

You can test this by printing something directly to bot streams and by fetching the root logger and shove some INFO s into it.

Another guess is, that your log4j jars somehow conflict with the slf4j stuff propagated by JBoss/Hibernate.