geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-5780) JUL output is lost after lost after application resets logging
Date Sun, 23 Jan 2011 20:22:43 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor updated GERONIMO-5780:
----------------------------------

    Attachment: GERONIMO-5780.patch

> JUL output is lost after lost after application resets logging
> --------------------------------------------------------------
>
>                 Key: GERONIMO-5780
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5780
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Logging
>    Affects Versions: 3.0-M2
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
>         Attachments: GERONIMO-5780.patch
>
>
> Some application may reset JUL logging with their own configuration. That means that
logging information from other applications or components using JUL might get lost or go to
a wrong place. 
> With JUL logging it is possible to detect when the configuration was reset and we can
use that to restore the root logger handler that PAX Logging has installed. That way if a
component resets logging we can warn about it and restore the root logger.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message