[jboss-jira] [JBoss JIRA] Reopened: (JBAS-8541) Deploying an application that has its own slf4j jars causes errors in the server log

[Nikita D (JIRA)]

     [ https://jira.jboss.org/browse/JBAS-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nikita D reopened JBAS-8541:
----------------------------



Could you please reconsider this ticket? This issue has already come up multiple times (see linked tickets) and it will keep coming up since more and more popular projects are adopting slf4j. For example, right now any application that uses Hibernate will trigger these errors when deployed on JBoss.

Here's a recap of all the suggested solutions so far:
 1. Remove the slf4j jars from the application. This is not an option if the slf4j version needed by the application is different than the one packaged with JBoss.
 2. Remove the JBoss slf4j jars. This is not an option if several applications are deployed to JBoss and one of them wants to use the JBoss slf4j jars. Also, it's not viable to tell a customer that they need to modify the app server's common jars just to deploy one additional application to an existing server running their apps.
 3. Change the classloading config for the app to exclude the JBoss slf4j jars. This is the real solution, but unfortunately it seems that this is not possible to configure out-of-the-box (see http://community.jboss.org/thread/156441).

Given the above, I think it's fair to say that there are 3 potential workarounds for this problem, but not an actual solution/fix.

For reference, these are the classloading wiki docs:
 * http://community.jboss.org/wiki/classloadingconfiguration
 * http://community.jboss.org/wiki/ClassLoadingOverview
 * http://community.jboss.org/wiki/JBossClassLoadingUseCases
 * http://community.jboss.org/wiki/JBoss5custommetadatafiles 


> Deploying an application that has its own slf4j jars causes errors in the server log
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-8541
>                 URL: https://jira.jboss.org/browse/JBAS-8541
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-5.1.0.GA
>            Reporter: Nikita D
>            Assignee: David Lloyd
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira