[jboss-jira] [JBoss JIRA] Resolved: (JBASM-36) Set system prop jboss.boot.server.log.level=DEBUG

[Shelly McGowan (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBASM-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shelly McGowan resolved JBASM-36.
---------------------------------

    Resolution: Done


Added  jboss.boot.server.log.level=DEBUG.  The log level can be overridden with the same property, logThreshold,  as done with jboss.server.log.threshold; ex:
server name="all" host="${node0}" logThreshold="TRACE"

> Set system prop jboss.boot.server.log.level=DEBUG
> -------------------------------------------------
>
>                 Key: JBASM-36
>                 URL: https://jira.jboss.org/jira/browse/JBASM-36
>             Project: JBoss AS Server Manager
>          Issue Type: Feature Request
>            Reporter: Brian Stansberry
>            Assignee: Shelly McGowan
>            Priority: Minor
>             Fix For: 1.0.4.GA
>
>
> See http://community.jboss.org/wiki/JBossBootLogging for background
> Property jboss.boot.server.log.level controls what goes in the boot.log, which currently covers almost the entire server start. AS trunk now has this logging at INFO by default, which means we don't see much startup detail in testsuite logs. Setting jboss.boot.server.log.level=DEBUG will restore the level of startp/shutdown logging we were seeing in 6.0.0.M1 and Branch_5_x.

-- 
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