You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Justin Heesemann (JIRA)" <ji...@apache.org> on 2016/11/03 08:27:58 UTC
[jira] [Created] (CAMEL-10439) Kafka Consumer cannot load class
RangeAssignor in Weblogic/JEE
Justin Heesemann created CAMEL-10439:
----------------------------------------
Summary: Kafka Consumer cannot load class RangeAssignor in Weblogic/JEE
Key: CAMEL-10439
URL: https://issues.apache.org/jira/browse/CAMEL-10439
Project: Camel
Issue Type: Bug
Components: camel-kafka
Affects Versions: 2.18.0
Environment: Weblogic 12
Reporter: Justin Heesemann
Seems like the fix for CAMEL-10069 makes it impossible to use the kafka consumer when deployed in a JEE environment (in my case weblogic).
Setting the classloader to null (ie setting the system classloader) effectively removes the kafka classes from the classpath (at least this is what I think happens..).
org.apache.kafka.common.KafkaException: org.apache.kafka.clients.consumer.RangeAssignor ClassNotFoundException exception occured
Apparently they fixed some classloading issues with kafka-clients 0.10.1.0 .. so maybe this might be a better solution than to tamper with the classloaders?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)