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 2020/06/08 04:59:00 UTC

[jira] [Updated] (CAMEL-15157) DefaultUnitOFWork is holding thread in Camel 3

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

Claus Ibsen updated CAMEL-15157:
--------------------------------
    Priority: Minor  (was: Major)

> DefaultUnitOFWork is holding thread in Camel 3
> ----------------------------------------------
>
>                 Key: CAMEL-15157
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15157
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-base
>    Affects Versions: 3.2.0
>            Reporter: Minal
>            Priority: Minor
>
> we use Persistent Custom MDC Logging in Apache Camel as mentioned in this link.
> h1. [https://developers.redhat.com/blog/2016/05/12/persistent-custom-mdc-logging-in-apache-camel/]
>  
> After we upgrade Apache Camel version from 2.25.0 to 3.2.0 , we started seeing issue of thread is being hold for 30-40 ms when calling CustomUnitOFWork which internally call MDCUnitOfWork. 
>  
> What we noticed is thread hold time is keep on increasing every hour and not able to understand this issue. 



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