zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajiv Bandi (Jira)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2342) Migrate to Log4J 2.
Date Tue, 27 Aug 2019 15:00:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916784#comment-16916784
] 

Rajiv Bandi commented on ZOOKEEPER-2342:
----------------------------------------

Hi All,

         Based on the above discussion, the blocker seems to be LOG4J2-63 (support
for log4j 1.x properties or xml config in log4j2). As log4j2 is backward incompatible with
log4j 1.x, isn't upgrading from log4j 1.x to log4j2 a backward incompatible move? Can you
please target the log4j2 upgrade in a major release where the only backward incompatible change
is the log4j2 configuration?

Thanks

Rajiv

 

> Migrate to Log4J 2.
> -------------------
>
>                 Key: ZOOKEEPER-2342
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
>             Project: ZooKeeper
>          Issue Type: Bug
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Major
>             Fix For: 3.6.0
>
>         Attachments: ZOOKEEPER-2342.001.patch
>
>
> ZOOKEEPER-1371 removed our source code dependency on Log4J.  It appears that this also
removed the Log4J SLF4J binding jar from the runtime classpath.  Without any SLF4J binding
jar available on the runtime classpath, it is impossible to write logs.
> This JIRA investigated migration to Log4J 2 as a possible path towards resolving the
bug introduced by ZOOKEEPER-1371.  At this point, we know this is not feasible short-term.
 This JIRA remains open to track long-term migration to Log4J 2.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message