[
https://issues.apache.org/jira/browse/CAMEL-22717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039804#comment-18039804
]
Pasquale Congiusti commented on CAMEL-22717:
--------------------------------------------
Was this working before 4.10 by any chance?
The problem is the clearing of MDC context which is not hierarchical. When you
include the interceptor, the execution of the direct route is wrapped correctly
by a set-->process-->unset , but it is affected by the other pipelines tasks,
becoming set1-->set2-->unset2-->process-->unset1 ending up clearning the MDC. I
need to verify if we can introduce a stack based approach which should solve
this issue.
> MDC values get lost at interceptedSendTo Endpoint
> -------------------------------------------------
>
> Key: CAMEL-22717
> URL: https://issues.apache.org/jira/browse/CAMEL-22717
> Project: Camel
> Issue Type: Bug
> Components: came-core
> Affects Versions: 4.10.6, 4.14.2, 4.15.0
> Reporter: Daniel Fritsch
> Assignee: Pasquale Congiusti
> Priority: Minor
> Fix For: 4.17.0
>
> Attachments: demo-intercept-and-mdc.zip, screenshot-1.png
>
>
> when a endpoint logs and on this endpoint is a interceptSendTo active, then
> at the execution of the endpoints processor [can be any endpoint type
> (bean/cxfrs/...)] right after the interceptSendTo route the default MDC
> values (like camel.breadcrumbId) are not present. After the endpoint they are
> present again.
> note: This bug happens not when the route is transacted.
>
> see: Screenshot of the log
> !screenshot-1.png|width=537,height=449!
> see: demo project (i use a local activemq cause i tested it also with
> transacted)
> [^demo-intercept-and-mdc.zip]
>
> instead of the from("cMQConnectionFactory1:queue:test") line without
> transaction, it can be used this line also:
> {code:java}
> from("timer:mytimer?repeatCount=1") {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
