[
https://issues.apache.org/jira/browse/ZOOKEEPER-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053811#comment-15053811
]
Chris Nauroth commented on ZOOKEEPER-2342:
------------------------------------------
bq. Does it mean that the properties file needs to be rewritten during a
rolling upgrade from say branch 3.4 to branch 3.5?
Yes, that's correct. Instead of using a log4j.properties file with the Log4J 1
syntax, it looks like you'd now need a log4j2.properties file, written in the
new Log4J 2 syntax. For administrators who have customized their
log4j.properties file to do something different from what we ship, they'd need
to prepare an equivalent log4j2.properties before the upgrade.
There are more details on this in the Log4J 2 configuration documentation,
especially the sections on "Automatic Configuration" and "Configuration with
Properties".
http://logging.apache.org/log4j/2.x/manual/configuration.html
> ZooKeeper cannot write logs, because there is no SLF4J binding available on
> the runtime classpath.
> --------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2342
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2342
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Chris Nauroth
> Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
