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

Vladimir Dobos updated CAMEL-16857:
-----------------------------------
    Description: 
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 [link 
|http://example.com/]] [https://github.com/vdobos-tr/camel-kafka-on-error-leak] 
[|http://example.com/]].
 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.

  was:
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 [link 
[https://github.com/vdobos-tr/camel-kafka-on-error-leak|http://example.com/]].
 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.


> 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 [link 
> |http://example.com/]] 
> [https://github.com/vdobos-tr/camel-kafka-on-error-leak] 
> [|http://example.com/]].
>  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)

Reply via email to