[
https://issues.apache.org/jira/browse/KARAF-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-3710.
-----------------------------------------
Resolution: Cannot Reproduce
Maybe I don't use the right test case, but I'm not able to reproduce. Can you
illustrate a bit if it's still the case on Karaf 4.2.x ?
> 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
>
> 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
(v8.3.2#803003)
