[KAFKA-2221] Log the entire cause which caused a reconnect in the SimpleConsumer

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.9.0.1
• Assignee: Jaikiran Pai
• Reporter: Jaikiran Pai
• Created: 27/May/15 03:41
• Updated: 29/Jan/16 04:25
• Resolved: 29/Jan/16 04:25

Description

Currently if the SimpleConsumer goes for a reconnect, it logs the exception's message which caused the reconnect. However, in some occasions the message in the exception can be null, thus making it difficult to narrow down the cause for the reconnect. An example of this can be seen in this user mailing list thread http://mail-archives.apache.org/mod_mbox/kafka-users/201505.mbox/%3CCABME_6T%2Bt90%2B-eQUtnu6R99NqRdMpVj3tqa95Pygg8KOQSNppw%40mail.gmail.com%3E

kafka.consumer.SimpleConsumer: Reconnect due to socket error: null.

It would help narrowing down the problem if the entire exception stacktrace was logged.