Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-1632

Multiple SLF4J bindings found in classpath upon instance creation

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • None
    • AMQ 7.2.0.GA
    • logging, packaging
    • Compatibility/Configuration, User Experience
    • Low
    • Hide
      Show
      download http://download.eng.bos.redhat.com/devel/candidates/amq/AMQ-BROKER-7.2.0.CR3/ unzip AMQ-BROKER-7.2.0.CR3 amq-broker-7.2.0/bin/artemis create newbroker answer default questions observe slf4j error output

    Description

      Upon broker instance creation, following output is seen.

      1@dhcp-145-200 0 opt [0]$ amq-broker-7.2.0/bin/artemis create newbroker
      Creating ActiveMQ Artemis instance at: /opt/newbroker
      
      --user: is a mandatory property!
      Please provide the default username:
      admin
      
      --password: is mandatory with this configuration:
      Please provide the default password:
      
      
      --allow-anonymous | --require-login: is a mandatory property!
      Allow anonymous access?, valid values are Y,N,True,False
      Y
      
      Auto tuning journal ...
      SLF4J: Class path contains multiple SLF4J bindings.
      SLF4J: Found binding in [jar:file:/opt/amq-broker-7.2.0/lib/slf4j-jboss-logmanager-1.0.3.GA-redhat-2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
      SLF4J: Found binding in [jar:file:/opt/amq-broker-7.2.0/lib/slf4j-jboss-logmanager-1.0.4.GA.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.Slf4jLoggerFactory]
      done! Your system can make 7.58 writes per millisecond, your journal-buffer-timeout will be 132000
      
      You can now start the broker by executing:  
      
         "/opt/newbroker/bin/artemis" run
      
      Or you can run the broker in the background using:
      
         "/opt/newbroker/bin/artemis-service" start
      
      

      This 'slf4j' output (slightly different, but very similar problem ) was fixed in previous AMQ 7.1.0 release ( see linked issue, ENTMQBR-821 )

      This output ideally, should not be shown as part of broker instance creation ( first thing customer will see )

      Attachments

        Issue Links

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rh_sdavey Sean Davey (Inactive)
              Sean Davey Sean Davey (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 2 days
                  2d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified