[
https://issues.apache.org/jira/browse/KAFKA-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984523#comment-13984523
]
Jun Rao commented on KAFKA-1354:
--------------------------------
That makes sense. The problem is that currently the kafka jar is for both the
sever and the client. We are creating the new clients in a separate jar.
Perhaps we can revisit this when the old clients are phased out.
> 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)
