[CAMEL-13842] Improve Logging on KafkaConsumer when KafkaException is Thrown

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Component/s: camel-kafka
• Estimated Complexity: Novice
• Assignee: Ramu
• Reporter: Leonardo Vasconcellos
• Created: 09/Aug/19 05:21
• Updated: 05/Sep/19 03:20
• Resolved: 05/Sep/19 03:20

Description

The Kafka Camel component "hides" the stacktrace of exceptions occurring in the following point. 

components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java
...
log.warn("KafkaException consuming {} from topic {}. Will attempt to re-connect on next run", threadId, topicName);
reConnect = true;
...

It makes difficult to know the root of the KafkaException exception (NullPointer for example) by seeing the log.

Maybe change the log.warn to handtleException so we can see the full stack trace in the log, since LoggingExceptionHandler logs the full stack trace.

...
getExceptionHandler().handleException("KafkaException consuming " + threadId + " from topic " + topicName + ". Will attempt to re-connect on next run", e);
reConnect = true;
...