[arquillian-issues] [JBoss JIRA] (ARQ-913) Allow the log threshold to be configured for managed JBoss AS 6

[Dan Allen (JIRA)]

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

Dan Allen reassigned ARQ-913:
-----------------------------

    Assignee: Dan Allen

    
> Allow the log threshold to be configured for managed JBoss AS 6
> ---------------------------------------------------------------
>
>                 Key: ARQ-913
>                 URL: https://issues.jboss.org/browse/ARQ-913
>             Project: Arquillian
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: JBoss AS Containers
>    Affects Versions: jbossas_1.0.0.CR3
>            Reporter: Dan Allen
>            Assignee: Dan Allen
>
> The managed JBoss AS 6 adapter does not explicitly set the log threshold on the server controller. As a result, the server controller defaults the log threshold to DEBUG. You can see this setting reflected in the start command:
> {code}
> -Djboss.server.log.threshold=DEBUG
> {code}
> This threshold produces an enormous amount of log statements, which get redirected to the server/default/log/output.log file.
> Here's a comparison of the log file size between various threshold levels:
> DEBUG: 2.2 MB
> INFO: 80 KB
> ERROR: 76 KB
> The server starts much faster when the threshold is higher, so we should allow this setting to be configured. If a configuration value is not set, the level should default to INFO (rather than the fallback of DEBUG).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira