-
1. Re: trace logging for jboss
weston.price Dec 6, 2006 7:29 PM (in response to btogo)You either have a typo (Pool not Poll) or some other configuration issue in your log4j.xml file.
It should be<category name="org.jboss.resource.connectionmanager.JBossManagedConnectionPool"> <priority value="TRACE" class="org.jboss.logging.XLevel"/> </category>
-
2. Re: trace logging for jboss
btogo Dec 6, 2006 10:49 PM (in response to btogo)Thanks for your reply. But it is a typo in my posting. I do have Pool in the log4j.xml file.
Anything else you may think of?
Thanks, -
3. Re: trace logging for jboss
weston.price Dec 6, 2006 10:57 PM (in response to btogo)Can I see the definition of
JBOSSLOG -
4. Re: trace logging for jboss
btogo Dec 7, 2006 8:21 AM (in response to btogo)Sure.
<appender name="JBOSSLOG" class="org.apache.log4j.DailyRollingFileAppender"> <param name="File" value="/home/eta/server/log/connection-jboss.log"/> <param name="Append" value="true"/> <param name="Threshold" value="TRACE"/> <!-- Rollover at midnight each day or per size --> <param name="DatePattern" value="'.'yyyy-MM-dd"/> <!-- <param name="MaxFileSize" value="10MB"/> --> <!-- <param name="MaxBackupIndex" value="5"/> --> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/> </layout> </appender>
-
5. Re: trace logging for jboss
humbahe Jan 5, 2007 6:03 AM (in response to btogo)I have a similar problem since there are 2 different log4j.jars distributed with jboss (4.0.5).
The log4j-boot.jar in the "lib" folder contains a Logger, that is able to log "TRACE"-Messages.
The log4j.jar in the "server/**/lib" folders contains a Logger, that is NOT able to log "TRACE"-Messages.
Any attempts to replace the log4j-distributions in the "server/**/lib" folders ended in a log4j configuration error (could not parse url .../log4j.xml).
Has anyone an idea howto replace the log4j.jars? -
6. Re: trace logging for jboss
raviprk Jan 12, 2007 6:35 PM (in response to btogo)Remove the Threshold attribute from the appender config completely. I had the same problem, seems to be a mismatch between the int values of TRACE in log4j and JBoss.