[
https://issues.apache.org/jira/browse/CAMEL-13842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
LEONARDO ZANDOMENICO VASCONCELLOS updated CAMEL-13842:
------------------------------------------------------
Description:
The Kafka Camel component "hides" the stacktrace of exceptions occurring in the
following point.
{code:java}
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;
...{code}
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:
{code:java}
...
getExceptionHandler().handleException("KafkaException consuming " + threadId +
" from topic " + topicName + ". Will attempt to re-connect on next run", e);
reConnect = true;
...{code}
was:
The Kafka Camel component "hides" the stacktrace of exceptions occurring in the
following point.
{code:java}
components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java{code}
{code:java}
...
log.warn("KafkaException consuming {} from topic {}. Will attempt to re-connect
on next run", threadId, topicName);
reConnect = true;
...{code}
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:
{code:java}
...
getExceptionHandler().handleException("KafkaException consuming " + threadId +
" from topic " + topicName + ". Will attempt to re-connect on next run", e);
reConnect = true;
...{code}
> Improve Logging on KafkaConsumer when KafkaException is Thrown
> --------------------------------------------------------------
>
> Key: CAMEL-13842
> URL: https://issues.apache.org/jira/browse/CAMEL-13842
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Affects Versions: 3.0.0
> Reporter: LEONARDO ZANDOMENICO VASCONCELLOS
> Priority: Major
>
> The Kafka Camel component "hides" the stacktrace of exceptions occurring in
> the following point.
> {code:java}
> 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;
> ...{code}
> 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:
> {code:java}
> ...
> getExceptionHandler().handleException("KafkaException consuming " + threadId
> + " from topic " + topicName + ". Will attempt to re-connect on next run", e);
> reConnect = true;
> ...{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
