Class path contains multiple SLF4J bindings

[Alexander Jipa]

Hello,

I was playing around with confluent platform and stumbled upon the following problem that prevents me from starting Kafka Connect, both standalone and distributed.

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in [jar:file:/******************/confluent-3.0.0/share/java/kafka-serde-tools/slf4j-log4j12-1.7.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: Found binding in [jar:file:/******************/confluent-3.0.0/share/java/kafka/slf4j-log4j12-1.7.21.jar!/org/slf4j/impl/StaticLoggerBinder.class]

It looks like there are multiple SLF4J implementations in the classpath (It looks like there are 3: 1.7.5, 1.7.6, 1.7.21).

It's not that I cannot fix it be removing all of them but one from the distribution, but it seems like a bug to me (I believe only the app should have the actual dependency and others must use a provided scope for the slf4j dependency).

Is there a proper place I can raise the issue?

Thank you!

---

Cheers,

Alexander

[Ismael Juma]

Hi Alexander,

That warning is annoying, but it is harmless. It should not prevent Kafka Connect from starting, so it seems like the underlying problem is something else. Is there anything in the logs?

Ismael

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/8f8d9813-c5ef-4483-adc9-25e7312893c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alexander Jipa]

Turned out to be a configuration problem, wrong kafka brokers settings - but for some reason I wasn't getting any log messages until I removed redundant libraries.

Even though slf4j will pick up some random implementation - don't you think it's worth fixing?

Few less jars to load (regardless how small they are).

I can contribute :D

On Thursday, June 9, 2016 at 11:46:01 AM UTC-4, Ismael Juma wrote:

Hi Alexander,

That warning is annoying, but it is harmless. It should not prevent Kafka Connect from starting, so it seems like the underlying problem is something else. Is there anything in the logs?

Ismael

On Thu, Jun 9, 2016 at 3:54 PM, Alexander Jipa <alexand...@gmail.com> wrote:

Hello,

I was playing around with confluent platform and stumbled upon the following problem that prevents me from starting Kafka Connect, both standalone and distributed.

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in [jar:file:/******************/confluent-3.0.0/share/java/kafka-serde-tools/slf4j-log4j12-1.7.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: Found binding in [jar:file:/******************/confluent-3.0.0/share/java/kafka/slf4j-log4j12-1.7.21.jar!/org/slf4j/impl/StaticLoggerBinder.class]

It looks like there are multiple SLF4J implementations in the classpath (It looks like there are 3: 1.7.5, 1.7.6, 1.7.21).

It's not that I cannot fix it be removing all of them but one from the distribution, but it seems like a bug to me (I believe only the app should have the actual dependency and others must use a provided scope for the slf4j dependency).

Is there a proper place I can raise the issue?

Thank you!

---

Cheers,

Alexander

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.

[Pavel Martynov]

I have same issue with Control Center.

$ yum list installed | grep confluent

confluent-common.noarch               3.0.0-1                        @Confluent

confluent-control-center.noarch       3.0.0-1                        @Confluent

confluent-kafka-2.11.noarch           0.10.0.0-1                     @Confluent

confluent-rest-utils.noarch           3.0.0-1                        @Confluent

четверг, 9 июня 2016 г., 18:46:01 UTC+3 пользователь Ismael Juma написал:

Hi Alexander,

That warning is annoying, but it is harmless. It should not prevent Kafka Connect from starting, so it seems like the underlying problem is something else. Is there anything in the logs?

Ismael

On Thu, Jun 9, 2016 at 3:54 PM, Alexander Jipa <alexand...@gmail.com> wrote:

Hello,

I was playing around with confluent platform and stumbled upon the following problem that prevents me from starting Kafka Connect, both standalone and distributed.

SLF4J: Class path contains multiple SLF4J bindings.

SLF4J: Found binding in [jar:file:/******************/confluent-3.0.0/share/java/kafka-serde-tools/slf4j-log4j12-1.7.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]

SLF4J: Found binding in [jar:file:/******************/confluent-3.0.0/share/java/kafka/slf4j-log4j12-1.7.21.jar!/org/slf4j/impl/StaticLoggerBinder.class]

It looks like there are multiple SLF4J implementations in the classpath (It looks like there are 3: 1.7.5, 1.7.6, 1.7.21).

It's not that I cannot fix it be removing all of them but one from the distribution, but it seems like a bug to me (I believe only the app should have the actual dependency and others must use a provided scope for the slf4j dependency).

Is there a proper place I can raise the issue?

Thank you!

---

Cheers,

Alexander

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.