-
Bug
-
Resolution: Done
-
Minor
-
7.0.0.Alpha1
-
- For an EAR application, place the slf4j jars into the ear's lib directory.
- Deploy the app to JBoss.
- The slf4j error will reference the slf4j jars inside the ear and in JBOSS_HOME/common/lib.
If an application depends on a different version of slf4j than the one packaged with JBoss, the slf4j jars (api and impl) need to be included with the application. This results in the "multiple SLF4J bindings" error message:
00:34:25,247 ERROR [STDERR] SLF4J: Class path contains multiple SLF4J bindings.
00:34:25,247 ERROR [STDERR] SLF4J: Found binding in [vfszip:/C:/a/bin/jboss/jboss-5.1.0.GA/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class]
00:34:25,247 ERROR [STDERR] SLF4J: Found binding in [vfszip:/c:/a/ear/suite.ear/lib/slf4j-log4j12-1.5.8.jar/org/slf4j/impl/StaticLoggerBinder.class]
00:34:25,247 ERROR [STDERR] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
- is related to
-
JBPAPP-3898 Deploying of the unpacked RESTEasy war from EAP dist. causes errors in the server log
- Closed
-
JBPAPP-3951 Deploying an application that has its own config for SLF4J causes errors in the server log
- Closed
-
JBPAPP-4658 jboss-integration-testing examples produce slf4j error in log
- Closed
-
RIFTSAW-211 Log4j error at JBoss startup time: class path contains multiple SLF4J bindings.
- Closed