[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071520#comment-17071520
]
Ljubo Mamic commented on ZOOKEEPER-2342:
----------------------------------------
Hi,
Did anyone try to migrate log4j with the log4j-1.2-api bridge?
Is zookeeper compatible?
[http://logging.apache.org/log4j/2.x/manual/migration.html] Here it says:
h2. Migrating from Log4j 1.x
h3. Using the Log4j 1.x bridge
Perhaps the simplest way to convert to using Log4j 2 is to replace the log4j
1.x jar file with Log4j 2's log4j-1.2-api.jar. However, to use this
successfully applications must meet the following requirements:
# They must not access methods and classes internal to the Log4j 1.x
implementation such as Appenders, LoggerRepository or Category's callAppenders
method.
# They must not programmatically configure Log4j.
# They must not configure by calling the classes DOMConfigurator or
PropertyConfigurator.
Best Regards, Ljubo
> 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.7.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.4#803005)
