Claus Ibsen created CAMEL-27305:
-----------------------------------
Summary: camel-kafka-share - the share consumer stops without
logging an error when its poll fails with an Error
Key: CAMEL-27305
URL: https://issues.apache.org/jira/browse/CAMEL-27305
Project: Camel
Issue Type: Bug
Components: camel-kafka
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.24.0
When the poll of a Kafka share consumer (camel-kafka-share) fails with an
{{Error}} instead of an exception, the consumer thread ends without logging
anything. An example is a value deserializer whose generated classes cannot be
loaded ({{ExceptionInInitializerError}} or {{NoClassDefFoundError}}, see
CAMEL-27300).
The share client wraps only a {{RuntimeException}} of a deserializer in a
{{RecordDeserializationException}} ({{ShareCompletedFetch.parseRecord}} in
kafka-clients 4.4.0), so an {{Error}} is thrown out of {{poll}} as is.
{{KafkaShareFetchRecords}} handles only exceptions, and the task runs with
{{executor.submit}}, so the {{Error}} is kept in a {{Future}} that nobody reads:
* nothing is logged at WARN or ERROR, not even the "Terminating" line;
* the share consumer is closed (in the {{finally}} of {{run}}), so the health
check is DOWN, but it says "recovery in progress", has no error, and the
consumer never recovers.
This is the same gap as CAMEL-27298 in camel-kafka.
Expected: as in camel-kafka, the consumer thread logs what it does not handle
at ERROR and terminates with the error as the last error of its health check
("terminated ... restart route or application to recover"). A
{{VirtualMachineError}} is thrown on as is.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)