Details
-
Bug
-
Resolution: Done
-
Minor
-
A-MQ 7.0.0.ER7, A-MQ 7.0.0.ER8
-
None
-
- Simple run Artemis console on rhel with installed all dependencies.
- See to logs.
Description
I look for this "error" when i run artemis console:
INFO [org.apache.activemq.artemis.core.server] AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.2.0.amq-700002-redhat-1 [0.0.0.0, nodeID=b02ca3eb-f0cf-11e5-a525-525400549243] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
This is result of two available libs in classpath.
Here: _lib/
- _slf4j-api-1.7.12.redhat-1.jar
And here: /opt/lala/tmp/jetty-localhost-8161-artemis-plugin.war-_artemis-plugin-any-439588977228608448.dir/webapp/WEB-INF/lib/
- hawtio-plugin-mbean-1.4.redhat-621084.jar
- slf4j-api-1.7.12.redhat-1.jar
- log4j-1.2.17.redhat-1.jar
- slf4j-log4j12-1.7.12.redhat-1.jar
http://www.slf4j.org/codes.html#StaticLoggerBinder
*Failed to load class org.slf4j.impl.StaticLoggerBinder* This error is reported when the org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. This happens when no appropriate SLF4J binding could be found on the class path. Placing one (and only one) of slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path should solve the problem.
Solution:
So I think than is right way is have libs in lib folder (only one). My own opinion for any copying each time when it starts (for any redudency) is a bad solution. It's look as lot of wasted redundancy.
Attachments
Issue Links
- is related to
-
-
- Closed
-
