You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jens Kordowski (Jira)" <ji...@apache.org> on 2021/08/02 10:58:00 UTC

[jira] [Updated] (CAMEL-16832) camel-kafka - file descriptor leak

     [ https://issues.apache.org/jira/browse/CAMEL-16832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Kordowski updated CAMEL-16832:
-----------------------------------
    Issue Type: Bug  (was: Improvement)

> camel-kafka - file descriptor leak
> ----------------------------------
>
>                 Key: CAMEL-16832
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16832
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-kafka
>    Affects Versions: 3.11.0
>            Reporter: Jens Kordowski
>            Priority: Major
>
> The kafka consumer leaks, if the following conditions are met:
>  # consumer.poll() throws an exception (i.e. TLS handshake issue)
>  # PollOnError is set to RECONNECT
>  
> The run() method will execute another doInit(), if reconnect is set to true and the doInit() method will create another consumer. The "old" consumer does not unsubscribe and is not closed. It will hold on to 4 (I think) file descriptors, so after reiterating these reconnects many times, finally running into a "too many files" exception.
>  
> lr-x------ 1 root root 64 Aug 2 10:48 96 -> pipe:[19398]
> l-wx------ 1 root root 64 Aug 2 10:48 97 -> pipe:[19398]
> lrwx------ 1 root root 64 Aug 2 10:48 98 -> socket:[19399]
> lrwx------ 1 root root 64 Aug 2 10:48 99 -> anon_inode:[eventpoll]
>  
> Best regards
> Jens



--
This message was sent by Atlassian Jira
(v8.3.4#803005)