[
https://issues.apache.org/jira/browse/KAFKA-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984431#comment-13984431
]
Sharmarke Aden commented on KAFKA-1354:
---------------------------------------
As long as the client library uses slf4j api to log messages it only needs to
include the slf4j-api jar.
Broker Dependencies:
slf4j-api.jar
slf4j-log4j12.jar
log4j.jar
Client Dependencies:
slf4j-api
For third party dependencies that use other logging frameworks both the client
or the broker will also need to include slf4j bridge dependencies. For example,
if a third party library used by broker/client uses commons logging then you
should also distribute jcl-over-slf4j.jar
> Failed to load class "org.slf4j.impl.StaticLoggerBinder"
> --------------------------------------------------------
>
> Key: KAFKA-1354
> URL: https://issues.apache.org/jira/browse/KAFKA-1354
> Project: Kafka
> Issue Type: Bug
> Components: log
> Affects Versions: 0.8.1
> Environment: RHEL
> Reporter: RakeshAcharya
> Assignee: Jay Kreps
> Labels: newbie, patch, usability
> Fix For: 0.8.2
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> Getting below errors during Kafka startup
> 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.
> [2014-03-31 18:55:36,488] INFO Will not load MX4J, mx4j-tools.jar is not in
> the classpath (kafka.utils.Mx4jLoader$)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
