-
Bug
-
Resolution: Done
-
Minor
-
None
-
AMQ 7.2.0.GA
-
Compatibility/Configuration, User Experience
-
Low
-
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 )
- relates to
-
ENTMQBR-821 Missing slf4j logger classes in create instance module
- Closed