Debug messages in log4j

Load a log4j properties file:

PropertyConfigurator.configure("log4j.properties");

then in the file define what you want.

File might look like this:

log4j.rootCategory=DEBUG, LoggingFile

# Console is set to be a ConsoleAppender.

log4j.appender.Console=org.apache.log4j.ConsoleAppender

# LoggingFile is set to be a FileAppender.

log4j.appender.LoggingFile=org.apache.log4j.FileAppender

log4j.appender.LoggingFile.File=c:/sdca/logs/sdca.log

# LoggingFile uses PatternLayout.

log4j.appender.LoggingFile.layout=org.apache.log4j.PatternLayout

log4j.appender.LoggingFile.layout.ConversionPattern=%-4d [%-12t] %-5p %c %x - %m%n

So to stop all DEBUG messages change the line

log4j.rootCategory=DEBUG, LoggingFile

to

log4j.rootCategory=WARN, LoggingFile

JimDinosaura at 2007-7-15 16:53:56 >

Just today I went through the same horrible ordeal.

A couple notes about the default JBoss log4j.xml file it seems to affect the logging somewhat, from my understanding you SHOULD do this:

The <root> category should have a priority added:

<root>

<priority value="WARN" />

<appender-ref ref="CONSOLE"/>

<appender-ref ref="FILE"/>

</root>

That should set the default root category to only display WARNING messages. There's another category (name="org.jboss.resource.connectionmanager.JBossManagedConnectionPool") with priority set to TRACE. Change that to WARN or ERROR.

I set up my own server directory structure and left out the log4j.jar from the lib directory, so it hadn't been actually reading the XML file. Just something to watch out for.

Another thing I found was that the bin/run.jar has a log4j.properties file with rootCategory=DEBUG which generates the boot.log file. I un-jarred the file and set that to INFO, then re-jarred it... I couldn't get rid of all the DEBUG messages without doing so.

kzantowa at 2007-7-15 16:53:56 >