[jboss-jira] [JBoss JIRA] Closed: (JBAS-5116) Logger configuration wasn't updated on runtime
[ http://jira.jboss.com/jira/browse/JBAS-5116?page=all ]
Dimitris Andreadis closed JBAS-5116.
------------------------------------
Resolution: Incomplete Description
Assignee: (was: Scott M Stark)
You should be asking for help in the forums for this type of usage questions.
Open a JIRA only when you are certain this is a bug.
Logger configuration wasn't updated on runtime
----------------------------------------------
Key: JBAS-5116
URL: http://jira.jboss.com/jira/browse/JBAS-5116
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: JBossAS-4.2.0.GA
Environment: Solaris
Reporter: Keren Palatchi
Priority: Minor
While our system was up, we entered several changes to jboss-log4j.xml manually.
The changes were made in the 'Lmited Categories' section.
One change was to raise a category priority ( from INFO to WARN)
The second change was to add new category.
The changes didn't take affect after 60 sec (or more) as configured in
jboss-service.xml - RefreshPeriod entry.
The changes took affect only after jboss restart.
As I understood, jboss-log4j.xml should be polled every 60 sec and the confiuration
should be updated accordengly.
--
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