[jboss-jira] [JBoss JIRA] Commented: (JBAS-8530) Cannot enable debug logging for org.jboss.ha

[Scott Marlow (JIRA)]

    [ https://jira.jboss.org/browse/JBAS-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558743#action_12558743 ] 

Scott Marlow commented on JBAS-8530:
------------------------------------

I shortened the jboss-logging.xml file to http://pastebin.com/F95EyMMd and am now seeing org.jboss.ha output like:

2010-10-22 08:38:37,540 TRACE [org.jboss.ha.core.framework.server.CoreGroupCommunicationService$RpcHandler] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) destination list is empty, won't send 

This tells me that I either messed up the previous jboss-logging.xml contents with my prior attempt (http://pastebin.com/uDXNBBG3) or there is a bug exposed by the prior attempt.  

My command line for starting the AS is pretty basic for this successful run:

./run.sh -c tomcat-sso-cluster0 -b 127.0.0.2 -g DefaultPartition

Server profile tomcat-sso-cluster0 happens to be one of the unit test profiles that I'm working with.

> Cannot enable debug logging for org.jboss.ha
> --------------------------------------------
>
>                 Key: JBAS-8530
>                 URL: https://jira.jboss.org/browse/JBAS-8530
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>            Reporter: Scott Marlow
>            Assignee: David Lloyd
>             Fix For: 6.0.0.CR1
>
>
> I uncommented the org.jboss.ha section in jboss-logging.xml and didn't get debug logging output in server.log.  I also tried to hack the root-logger to debug.  
> My jboss-logging.xml is here http://pastebin.com/uDXNBBG3
> server.log is here http://pastebin.com/GugZg79M
> This is using the "all" profile.
> I ran the AS in a debugger and could see that the logger returned in org.jboss.ha.framework.server.HAServiceImpl has log.logger.loggerNode.effectLevel == 800 (INFO).
> It feels like this is a configuration issue of some sort as debug logging (via the root-logger change) is enabled for other some packages (like org.jboss.modcluster.ha).  
> Perhaps we just need more instructions in jboss-logging.xml explaining the additional configuration rules (if there are any) for enabling debug logging.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira