[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1472) Logging levels should never be set programatically, that's why we have log4j.xml!!!

[Julien Viet (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1472?page=all ]

Julien Viet updated JBPORTAL-1472:
----------------------------------

    Assignee: Sohil Shah  (was: Julien Viet)

> Logging levels should never be set programatically, that's why we have log4j.xml!!!
> -----------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1472
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1472
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.CR2, 2.4.1 SP1, 2.4.1 Final, 2.4 Final
>            Reporter: Galder Zamarreno
>         Assigned To: Sohil Shah
>            Priority: Blocker
>             Fix For: 2.6 Final
>
>
> I have spent two days with 3 support customers explaining them how to set TRACE level logs 
> for org.jboss.cache without success. They could never get it to work.
> Eventually, I have found the culprit:
> org.jboss.portal.cms.impl.jcr.JCRCMS
>       //set the proper logging level for JBossCache and JGroups
>       Logger cacheLogger = Logger.getLogger("org.jboss.cache");
>       cacheLogger.setLevel(Level.ERROR);
>       Logger groupsLogger = Logger.getLogger("org.jgroups");
>       groupsLogger.setLevel(Level.ERROR);
> This code should be removed immediately.

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