[jbpm-issues] [JBoss JIRA] Updated: (JBPM-3053) Class path contains multiple SLF4J bindings.

Class path contains multiple SLF4J bindings. -------------------------------------------- Key: JBPM-3053 URL: https://issues.jboss.org/browse/JBPM-3053 Project: jBPM Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: jBPM 5.0 Reporter: Michał K Assignee: Kris Verlaenen Priority: Minor Fix For: jBPM 5.1 I've installed and started jbpm 5.0. In jboss-5.1.0.GA/server/default/log/server.log i have: 2011-02-11 21:48:34,798 ERROR [STDERR] (main) SLF4J: Class path contains multiple SLF4J bindings. 2011-02-11 21:48:34,821 ERROR [STDERR] (main) SLF4J: Found binding in [vfszip:/opt/jbpm-5.0.0/jbpm-installer/jboss-5.1.0.GA/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class] 2011-02-11 21:48:34,821 ERROR [STDERR] (main) SLF4J: Found binding in [vfszip:/opt/jbpm-5.0.0/jbpm-installer/jboss-5.1.0.GA/server/default/deploy/drools-guvnor.war/WEB-INF/lib/slf4j-log4j12-1.6.0.jar/org/slf4j/impl/StaticLoggerBinder.class] 2011-02-11 21:48:34,821 ERROR [STDERR] (main) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. ... 2011-02-11 21:49:27,114 ERROR [STDERR] (main) log4j:ERROR A "org.jboss.logging.appender.FileAppender" object is not assignable to a "org.apache.log4j.Appender" variable. 2011-02-11 21:49:27,114 ERROR [STDERR] (main) log4j:ERROR The class "org.apache.log4j.Appender" was loaded by 2011-02-11 21:49:27,114 ERROR [STDERR] (main) log4j:ERROR [BaseClassLoader@4253c155{vfszip:/opt/jbpm-5.0.0/jbpm-installer/jboss-5.1.0.GA/server/default/deploy/jbpm-gwt-console-server.war/}] whereas object of type 2011-02-11 21:49:27,114 ERROR [STDERR] (main) log4j:ERROR "org.jboss.logging.appender.FileAppender" was loaded by [org.jboss.bootstrap.NoAnnotationURLClassLoader@196cd7d5]. 2011-02-11 21:49:27,114 ERROR [STDERR] (main) log4j:ERROR Could not instantiate appender named "FILE". Some problem is that in jboss-5.1.0.GA/common/lib is slf4j-api in version 1.5, in drools-guvnor.war is in 1.6.1 version. It is problem - see serwer.log