[jboss-jira] [JBoss JIRA] Closed: (JBAS-2412) Update the logging framework

Tue Jul 14 21:58:29 EDT 2009

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

David Lloyd closed JBAS-2412.
-----------------------------

    Fix Version/s:     (was: JBossAS-5.2.0.Beta1)
       Resolution: Done

Merged into 6.x.  Open a new JIRA if a backport to 5.2 is required

> Update the logging framework
> ----------------------------
>
>                 Key: JBAS-2412
>                 URL: https://jira.jboss.org/jira/browse/JBAS-2412
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>            Reporter: Scott M Stark
>            Assignee: David Lloyd
>             Fix For: JBossAS-6.0.0.Alpha1
>
>
> Its been a long time since we revisted the logging framework and the use of log4j as the default. I looked at having better seamless integration with the jdk java.util.logging framework using a port of the log4j appenders/layout to jdk handlers/formatters and the initial prototype is in head as mentioned in the linked forum thread.
> We need to reevaluate what the default logging implementation should be along with what updates the Log4jService needs. Some things to think about:
> 1. Using a log4j implementation that does not suffer from the current deadlock problem
> 2. How to nlog4j, slf4j, commons logging fit into the picture
> 3. Generalization of the Log4jService into one that works for whatever the default implementation is
> 3a. Add support for redirecting stderr, stdout to seperate log files instead of all loggers.

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