开发者

log4j: Doesn't reflect settings in log4j.properties

I have an Java-SE app with log4j over slf4j.

At some phase of development, it stopped logging DEBUG level, and I can't figure out why. I already excluded the causes I encountered earlier:

  • No WARNings
  • slf4j implementation used is log4j (AFAICT)
  • log4j.properties at right place (classpath root)
  • log4j.properties does end up in the .jar
  • The structure of the app didn't change
  • No log4j.properties or log4j.xml hidden in some .jar (like Weld-se-core has)
  • log4j.category. entries match (they didn't change since it worked)

Any ideas?

  log4j.rootLogger=DEBUG, stdout, file

  log4j.appender.stdout=org.apache.log4j.ConsoleAppender
  log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
  #log4j.appender.stdout.layout.ConversionPattern=%d %-5r %-5p [%c] (%t:%x) %m%n
  log4j.appender.stdout.layout.ConversionPattern=%d{HH:mm:ss.SSS} %-5p [%t] %c  %m%n

  log4j.appender.file=org.apache.log4j.DailyRollingFileAppender
  log4j.appender.file.File=JawaBot.log
  log4j.appender.开发者_如何学Pythonfile.layout=org.apache.log4j.PatternLayout
  log4j.appender.file.layout.ConversionPattern=%d{HH:mm:ss.SSS} %-5p [%t] %c  %m%n


  log4j.category.org = DEBUG
  log4j.category.org.jboss.jawabot = DEBUG
  log4j.category.org.jboss.jawabot.irc = DEBUG


  log4j.category.org.mortbay.log = WARN
  log4j.category.org.apache.wicket = INFO

  log4j.category.org.jboss.weld = DEBUG
  #log4j.category.org.jboss.weld.bootstrap = DEBUG
  log4j.category.org.jboss.weld.environment.se.jpa = DEBUG
0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜