[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17482444#comment-17482444
]
Hadriel Kaplan commented on ZOOKEEPER-2342:
-------------------------------------------
There is an alternative to migrating to log4j2: use
[reload4j|https://reload4j.qos.ch] instead.
Reload4j fixes the CVEs from log4j1, and is a drop-in replacement for log4j1.
(It's a fork of log4j1 that just fixes CVEs)
You don't have to modify any properties files/config or code at all.
Just remove the old `log4j-*.jar` and `slf-*.jar` jar files, and replace them
with
[slf4j-api-1.7.35.jar|https://repo1.maven.org/maven2/org/slf4j/slf4j-api/1.7.35/],
[slf4j-reload4j-1.7.35.jar|https://repo1.maven.org/maven2/org/slf4j/slf4j-reload4j/1.7.35/]
and
[reload4j-1.2.18.3.jar|https://repo1.maven.org/maven2/ch/qos/reload4j/reload4j/1.2.18.3/].
Note: if you use Ivy package manager, you might also need to modify the
dependency listings in ivy.xml - I'm not sure because I don't use it.
> 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.8.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.20.1#820001)
