[jira] [Updated] (KARAF-3710) BootstrapLogManager should first check if there's already a handler

["Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>]

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

Jean-Baptiste Onofré updated KARAF-3710:
----------------------------------------
    Fix Version/s: 4.2.7
                   4.3.0

> BootstrapLogManager should first check if there's already a handler
> -------------------------------------------------------------------
>
>                 Key: KARAF-3710
>                 URL: https://issues.apache.org/jira/browse/KARAF-3710
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf
>    Affects Versions: 3.0.3
>            Reporter: Raúl Kripalani
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 4.3.0, 4.2.7
>
>
> BootstrapLogManager should first check whether there are already handlers associated to the JUL logger. If so, it should not create a new one.
> We have a situation where the SimpleFileLock is configured with a start level threshold of 55, therefore ops4j pax logging has already initialised and it has taken over JUL through its JdkHandler.
> Then comes the BootstrapLogManager and decides to add a new Handler, despite the fact that there is already a root handler configured in JUL.
> This leads to two handlers on the SimpleFileLock logger: pax logging's {{JdkHandler}} and Karaf's {{BootstrapLogManager.SimpleFileHandler}}.
> The latter is not even configurable by means of a java.util.logging.properties (to my knowledge).
> I think that the BootstrapLogManager is no longer necessary, given that Karaf comes bundled with ops4j pax logging OOTB.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)