[jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1472) Logging levels should never be set programatically, that's why we have log4j.xml!!!
[ http://jira.jboss.com/jira/browse/JBPORTAL-1472?page=all ]
Sohil Shah resolved JBPORTAL-1472.
----------------------------------
Fix Version/s: 2.4.2 Final
Resolution: Done
A patch has been committed both to the trunk (Portal 2.6) and Portal 2.4 branch.
See the SVN commits tab for details
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, 2.4.2 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