[ 
https://issues.apache.org/jira/browse/CAMEL-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17129835#comment-17129835
 ] 

Minal edited comment on CAMEL-15157 at 6/9/20, 11:59 PM:
---------------------------------------------------------

[~davsclaus] This issue is extremely hard to re-produce, I read about known MDC 
issue in Camel 3 upgrade guide : 
[https://camel.apache.org/manual/latest/camel-3-migration-guide.html]

I don't understand the details of this issue in MDC. How do I get more details 
around it? At the same time if you can guide me with all known issue with Camel 
3 with that I might be able to co-relate this issue.


was (Author: bhalodi):
This issue is extremely hard to re-produce, I read about known MDC issue in 
Camel 3 upgrade guide : 
[https://camel.apache.org/manual/latest/camel-3-migration-guide.html]

I don't understand the details of what is known as an issue in MDC. How do I 
get more details around it? At least if you can guide me with some known issue 
with Camel 3 then I might be able to co-relate.

> 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-core
>    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)

Reply via email to