[
https://issues.apache.org/jira/browse/KARAF-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872080#comment-16872080
]
Jean-Baptiste Onofré edited comment on KARAF-6344 at 6/25/19 7:01 AM:
----------------------------------------------------------------------
Thanks for the report, I gonna fix at PAXLOGGING and cut a new release. The
purpose of the change is to avoid unnecessary refresh due to optional imports.
I introduced pax-logging extra to provide the imports. Let me test the use case
with AsyncLogger.
was (Author: jbonofre):
Thanks for the report, I gonna fix at PAXLOGGING and cut a new release.
> AsyncLogger fails due to bug in pax-logging
> -------------------------------------------
>
> Key: KARAF-6344
> URL: https://issues.apache.org/jira/browse/KARAF-6344
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.6
> Reporter: Rico Neubauer
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Labels: logging
> Fix For: 4.3.0, 4.2.7
>
>
> Just as reference:
> Karaf 4.2.6 updated to pax-logging 1.10.2, which introduced this regression:
> [https://ops4j1.jira.com/browse/PAXLOGGING-260]
> This leads to the logger breaking if e.g. Karaf gets configured for async
> logging _log4j2.rootLogger.type = asyncRoot_ in logging config. Exception
> below.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
