[jboss-jira] [JBoss JIRA] Commented: (JBAS-6205) Make server.log logging level configurable via system property

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on JBAS-6205:
----------------------------------------

Note that I don't intend to change the default away from DEBUG as part of this JIRA. That will require changing all the testsuite server configs to add -Djboss.server.log.level=DEBUG, and I'm not signing up for that as part of this JIRA. :-)

> Make server.log logging level configurable via system property
> --------------------------------------------------------------
>
>                 Key: JBAS-6205
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6205
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-5.0.0.GA
>
>
> Add <param name="Threshold" value="${jboss.server.log.level}"/> to the FILE appender config in jboss-log4j.xml.
> Log4j performs a system property substitution (see org.apache.log4j.xml.DomConfigurator.subst()). It doesn't seem to support our default value syntax, e.g. {jboss.server.log.level:DEBUG}, but starting the AS w/o setting the system property results in DEBUG logging.
> If we want a default other than DEBUG (or don't like counting on log4j to use DEBUG if the property isn't set), we can check the system property in Log4jService and set it if not set.

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