Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.20.0
-
None
-
Unknown
Description
When an exception is thrown by the org.apache.kafka.clients.consumer.KafkaConsumer constructor when instantiated by the KafkaConsumer inner class KafkaFetchRecords, the exception is not logged, nor propagated. This can happen, for example, if the key or the value deserializer class names are incorrect, or the class is not found by the class loader.
I would expect the exception here should cause the endpoint to fail initializing, or at a minimum, the exception should be logged. The fact that nothing is logged and the route is started without any apparent error, is misleading and very hard to troubleshoot.
Attachments
Issue Links
- is related to
-
CAMEL-17131 camel-kafka - JMX MBean InstanceAlreadyExistsException thrown
- Resolved