org.reflections.ReflectionsException

[Robin Moffatt]

Confluent Platform 3.0.0

I've previously been playing around with the Eneco twitter connector, but my current config (see gist) is simply to send an existing topic to HDFS. This topic is not created by the eneco twitter connector but a completely separate process (logstash). But, when I run Kafka Connect I get a warning: 

[2016-07-20 11:45:02,581] WARN could not get type for name com.eneco.trading.kafka.connect.twitter.TwitterSourceConnector from any class loader (org.reflections.Reflections:384)
org.reflections.ReflectionsException: could not get type for name com.eneco.trading.kafka.connect.twitter.TwitterSourceConnector
        at org.reflections.ReflectionUtils.forName(ReflectionUtils.java:378)
        at org.reflections.ReflectionUtils.forNames(ReflectionUtils.java:397)
        at org.reflections.Reflections.getSubTypesOf(Reflections.java:367)
        at org.apache.kafka.connect.runtime.AbstractHerder.connectorPlugins(AbstractHerder.java:270)
        at org.apache.kafka.connect.runtime.AbstractHerder$1.run(AbstractHerder.java:377)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: com.eneco.trading.kafka.connect.twitter.TwitterSourceConnector
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at org.reflections.ReflectionUtils.forName(ReflectionUtils.java:376)
        ... 5 more

Is this warning anything that needs fixing? And where's this reference to eneco coming from if not my configuration files? 

thanks!

[Ewen Cheslack-Postava]

We use reflections to search the classpath for connectors. I'm not sure how it is finding that class name but then isn't able to locate the class, but if it isn't affecting your ability to instantiate the connector then it should be fine. Note that you'll always see this because we proactively scan the classpath on startup (i.e. not tied to creating any specific connector or handling any particular REST API request).

-Ewen

--
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/c86df674-5801-4f99-bb6b-03ad6f24e9c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks,
Ewen

[Robin Moffatt]

Thanks, good to know.

To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/CAE1jLMPcjbLk22B_%3DsCojcwCotm84Dw8Kpkoq6YQu8nS69m7VA%40mail.gmail.com.