You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mike Grimes (JIRA)" <ji...@apache.org> on 2015/11/11 09:53:11 UTC
[jira] [Created] (OOZIE-2399) Oozie client class path contains
multiple SLF4J bindings
Mike Grimes created OOZIE-2399:
----------------------------------
Summary: Oozie client class path contains multiple SLF4J bindings
Key: OOZIE-2399
URL: https://issues.apache.org/jira/browse/OOZIE-2399
Project: Oozie
Issue Type: Bug
Components: client, scripts
Affects Versions: 4.2.0
Reporter: Mike Grimes
Priority: Minor
Fix For: trunk
Running the oozie CLI causes the following SLF4J warning to be shown (note this is on a brand new build - freshly extracted distro tarball):
[root@183bd1d9e976 oozie-4.2.0]# ./bin/oozie admin -status --oozie http://localhost:11000/oozie
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/root/oozie-4.2.0/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/root/oozie-4.2.0/lib/slf4j-simple-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
I'm pretty sure this was introduced in https://issues.apache.org/jira/browse/OOZIE-1876 as the client now extracts all jars in the war file to the lib/ directory, causing there to be two bindings:
[root@183bd1d9e976 oozie-4.2.0]# ls lib | grep slf4j
slf4j-api-1.6.6.jar
slf4j-log4j12-1.6.6.jar
slf4j-simple-1.6.6.jar
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)