[
https://issues.apache.org/jira/browse/ZOOKEEPER-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554205#comment-17554205
]
Chris Nauroth commented on ZOOKEEPER-4558:
------------------------------------------
Hello [~snehamin]. If you suspect this is an issue introduced by the Logback
migration (ZOOKEEPER-4427), then maybe a short-term workaround is to swap out
the logging back-end for Log4J 2. This is something I previously tested:
{code:java}
rm -f lib/logback*.jar
ln -sfn
~/.m2/repository/org/apache/logging/log4j/log4j-api/2.17.1/log4j-api-2.17.1.jar
lib/log4j-api-2.17.1.jar
ln -sfn
~/.m2/repository/org/apache/logging/log4j/log4j-core/2.17.1/log4j-core-2.17.1.jar
lib/log4j-core-2.17.1.jar
ln -sfn
~/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.17.1/log4j-slf4j-impl-2.17.1.jar
lib/log4j-slf4j-impl-2.17.1.jar
cat > conf/log4j2.properties <<EOF
appender.console.type = Console
appender.console.name = consoleLogger
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = %d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n
rootLogger.level = info
rootLogger.appenderRef.stdout.ref = consoleLogger
EOF
{code}
> zookeeper 3.8.0 java client logging enabled by default in Unix
> --------------------------------------------------------------
>
> Key: ZOOKEEPER-4558
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4558
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.8.0
> Reporter: PRASANTH KUMAR
> Priority: Major
> Attachments: catalina.out.rtf
>
>
> Unable to disable zookeeper java client logging in 3.8.0 version.
> Client logs are directed to the console and when running in tomcat the same
> gets updated in catalina.out.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
