Latest news

JavaRebel is a Jolt Awards finalist

The Jolt Awards finalists have been announced and JavaRebel is shortlisted in the Utilities category. ...

ZeroTurnaround at Devoxx

Devoxx is an annual European Java conference with a total of 3200 attendees from 35 countries and again has been completely sold o...

Christmas sale - everything is 40% off!

Christmas sale for ZeroTurnaround products has started and will last till 4th of January 2009. Everything is 40% off. ...

Every now and then for debugging purposes we need to see what the container’s classloaders are doing. On this page we will list the configuration options for different containers.

JBoss

Assuming the “default” configuration is used.

Log4j configuration file:
JBOSS_HOME/server/default/conf/jboss-log4j.xml

Add a category to the configuration file:

JBOSS 4.2

<category name=”org.jboss.mx.loading”>
<priority value=”TRACE”/>
<appender-ref ref=”CONSOLE”/>
<appender-ref ref=”FILE”/>
</category>

JBOSS 4.0

<category name=”org.jboss.mx.loading”>
<priority value=”TRACE” class=”org.jboss.logging.XLevel” />
<appender-ref ref=”CONSOLE”/>
<appender-ref ref=”FILE”/>
</category>

See the log under:
JBOSS_HOME/server/default/log/server.log

Jetty 6

Start Jetty with the line
java -DDEBUG -DDEBUG_PATTERNS=org.mortbay.jetty.webapp -DDEBUG_VERBOSE=1 -jar start.jar