[jira] Resolved: (GERONIMO-5780) JUL output is lost after application resets logging

["Jarek Gawor (JIRA)" <ji...@apache.org>]

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

Jarek Gawor resolved GERONIMO-5780.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0-M2

Committed patch to trunk (revision 1062609) and 3.0-M2 branch (revision 1062610).


> JUL output is 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
>             Fix For: 3.0-M2
>
>         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.