How do you Change a Package s Log Level using Log4j

Question

I ve encountered the following bug   http   issues apache org jira browse AXIS2-4363  It states the following      This error only occurs when log level   for org apache axiom is DEBUG so a   workaround is to set log level     DEBUG    My question is HOW do I go about doing that  I ve been scouring my directories for a properties file or something and I ve been looking to see if there was something I could set in code  but I really have no idea what I m doing  I m running a console app on my desktop right now while trying to get this to work    Update 1  I noticed that my Axis2 directory has its own log4j properties file in its root  Is this safely ignored or is it part of the solution  or part of the problem    Update 2  The root level log4j properties file is apprently not set correctly  Right now it looks like this   log4j rootLogger DEBUG  R  log4j logger org apache axiom WARN log4j appender R org apache log4j RollingFileAppender  log4j appender R MaxFileSize 10MB  log4j appender R MaxBackupIndex 10  log4j appender R layout org apache log4j PatternLayout  log4j appender R layout ConversionPattern  p  t  c -  m n   but that is apparently wrong as this code returns  Log level is null    System out println  Log level is     logger getLevel       For now I am setting the log level in code using   Logger logger   Logger getLogger  org apache axiom    logger setLevel Level WARN

User · Answer

I encountered the exact same problem today, Ryan.

In my src (or your root) directory, my log4j.properties file now has the following addition

# https://issues.apache.org/jira/browse/AXIS2-4363
log4j.category.org.apache.axiom=WARN

Thanks for the heads up as to how to do this, Benjamin.

User · Answer

This work for my   log4j logger org hibernate type trace   Also can try   log4j category org hibernate type trace

User · Answer

set the system property log4j debug true  Then you can determine where your configuration is running amuck

User · Answer

Which app server are you using   Each one puts its logging config in a different place  though most nowadays use Commons-Logging as a wrapper around either Log4J or java util logging   Using Tomcat as an example  this document explains your options for configuring logging using either option   In either case you need to find or create a config file that defines the log level for each package and each place the logging system will output log info  typically console  file  or db      In the case of log4j this would be the log4j properties file  and if you follow the directions in the link above your file will start out looking like   log4j rootLogger DEBUG  R  log4j appender R org apache log4j RollingFileAppender  log4j appender R File   catalina home  logs tomcat log  log4j appender R MaxFileSize 10MB  log4j appender R MaxBackupIndex 10  log4j appender R layout org apache log4j PatternLayout  log4j appender R layout ConversionPattern  p  t  c -  m n   Simplest would be to change the line   log4j rootLogger DEBUG  R   To something like   log4j rootLogger WARN  R   But if you still want your own DEBUG level output from your own classes add a line that says   log4j category com mypackage DEBUG   Reading up a bit on Log4J and Commons-Logging will help you understand all this

User · Answer

I just encountered the issue and couldn t figure out what was going wrong even after reading all the above and everything out there  What I did was   Set root logger level to WARN Set package log level to DEBUG   Each logging implementation has it s own way of setting it via properties or via code lot of help available on this   Irrespective of all the above I would not get the logs in my console or my log file  What I had overlooked was the below           All I was doing with the above jugglery was controlling only the production of the logs at root package class etc   left of the red line in above image  But I was not changing the way displaying consumption of the logs of the same  right of the red line in above image  Handler Consumption  is usually defaulted at INFO  therefore your precious debug statements wouldn t come through  Consumption displaying is controlled by setting the log levels for the Handlers ConsoleHandler FileHandler etc     So I went ahead and set the log levels of all my handlers to finest and everything worked   This point was not made clear in a precise manner in any place   I hope someone scratching their head  thinking why the properties are not working will find this bit helpful

[java] How do you Change a Package's Log Level using Log4j?

Examples related to java

Examples related to logging

Examples related to log4j

Examples related to axis2

Examples related to axiom