[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated ZOOKEEPER-2342:
-------------------------------------
Priority: Major (was: Blocker)
Fix Version/s: (was: 3.5.2)
Description:
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.
was: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, the it is
impossible to write logs.
Summary: Migrate to Log4J 2. (was: ZooKeeper cannot write logs,
because there is no SLF4J binding available on the runtime classpath.)
ZOOKEEPER-2393 now tracks restoring the SLF4J binding on the runtime classpath
as a blocker for 3.5.2. I have downgraded priority on this issue to major and
retargeted it to 3.6.0 for long-term tracking of Log4J 2 migration.
> 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
> 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
(v6.3.4#6332)
