You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/09/03 10:09:00 UTC
[jira] [Resolved] (CAMEL-16857) breakOnFirstError causes thread and
memory leaks in camel-kafka
[ https://issues.apache.org/jira/browse/CAMEL-16857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-16857.
---------------------------------
Resolution: Fixed
> breakOnFirstError causes thread and memory leaks in camel-kafka
> ---------------------------------------------------------------
>
> Key: CAMEL-16857
> URL: https://issues.apache.org/jira/browse/CAMEL-16857
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
> Affects Versions: 3.11.1
> Reporter: Vladimir Dobos
> Priority: Major
> Fix For: 3.11.2, 3.12.0
>
> Attachments: VisualVM_leak.png, VisualVM_leak_threads.png
>
>
> When breakOnfirstError is enabled in camel-kafka, there is visible thread leak (one hung heartbeat thread per kafka client restart/route retry) in underlying kafka client, accompanied by small memory leak, for extreme example - see attached VisualVM screenshots).
> Example application used for screenshot can be found in [https://github.com/vdobos-tr/camel-kafka-on-error-leak].
> We are relatively new to kafka so im unable to determine, if its issue with underlying kafka client, or problem with the way camel handles reconnect after error.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)