camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arno Noordover (JIRA)" <>
Subject [jira] [Assigned] (CAMEL-10115) Kafka consumer stays running if no messages were received after shutdown start
Date Mon, 04 Jul 2016 10:24:11 GMT


Arno Noordover reassigned CAMEL-10115:

    Assignee: Arno Noordover

> Kafka consumer stays running if no messages were received after shutdown start
> ------------------------------------------------------------------------------
>                 Key: CAMEL-10115
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-kafka
>    Affects Versions: 2.17.1
>         Environment: Spring Boot 1.4.0.M3 with Tomcat
> Java 8
> Camel 2.17.1
>            Reporter: Vadym Chekrii
>            Assignee: Arno Noordover
> After triggering {{CamelContext#close()}} method the execution will reach {{org.apache.camel.component.kafka.KafkaConsumer#doStop}}
where the shutdown of the executor instance will be triggered and where in it's turn the interruption
of the submitted to the executor threads should happen (by reaching the native implementation
of Thread#interrupt())
> According to
interrupt method will only set a corresponding status to the thread, but will not terminate
> Problem is in the line {{}}:
> {{ConsumerRecords<Object, Object> records = consumer.poll(Long.MAX_VALUE);}}
> In the Kafka implementation of the poll method this will lead to almost infinite {{while}}
loop which is not checking the thread status and this loop will exit only in case of receiving
a message from a broker. Only after exciting the loop the interrupted status of the thread
will be discovered and the thread will be terminated.
> This leads to a couple of problems:
> 1. The KafkaConsumers remain alive until receiving at least one more message from the
> 2. As the CamelContext at this point of time is most likely already shut down, the received
message is not going to be processed, but will be acknowledged to the broker. So effectively
the message gets lost.
> A potential fix would be to either make the poll timeout reasonably small or configurable.

This message was sent by Atlassian JIRA

View raw message