Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-3951

Deploying an application that has its own config for SLF4J causes errors in the server log

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • TBD
    • EAP 5.0.1.CR1
    • RESTEasy
    • None
    • Release Notes

    Description

      Hi,
      I am assigning this issue to you because you were interested in the last issue with RESTEasy in EAP. If you are not right person, please reassign this issue back to me. Thank you.

      EAP 5.0.1 CR1 distribution contains unpacked war file for quick start. But if you use this unpacked war you will obtain following errors.

      EAP 5.0.1 CR1 distribution
      http://download.devel.redhat.com/devel/candidates/JBEAP5.0.0/5.0.1_CR1/

      Server log.
      09:16:43,468 ERROR [STDERR] SLF4J: Class path contains multiple SLF4J bindings.
      09:16:43,468 ERROR [STDERR] SLF4J: Found binding in [vfszip:xxxxx/eap-5.0.1-CR1/jboss-eap-5.0/jboss-as/server/default/deploy/resteasy.war/WEB-INF/lib/slf4j-simple.jar/org/slf4j/impl/StaticLoggerBinder.class]
      09:16:43,468 ERROR [STDERR] SLF4J: Found binding in [vfszip:xxxxxx/eap-5.0.1-CR1/jboss-eap-5.0/jboss-as/common/lib/slf4j-jboss-logging.jar/org/slf4j/impl/StaticLoggerBinder.class]
      09:16:43,468 ERROR [STDERR] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-3898 Deploying of the unpacked RESTEasy war from EAP dist. causes errors in the server log

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-4658 jboss-integration-testing examples produce slf4j error in log

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. RIFTSAW-211 Log4j error at JBoss startup time: class path contains multiple SLF4J bindings.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. AS7-8 Deploying an application that has its own slf4j jars causes errors in the server log

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              pslavice@redhat.com Pavel Slavicek
              pslavice@redhat.com Pavel Slavicek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: