[
https://issues.apache.org/jira/browse/CAMEL-22717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039879#comment-18039879
]
Pasquale Congiusti commented on CAMEL-22717:
--------------------------------------------
A first PR addressing the stack based management of MDC values:
https://github.com/apache/camel/pull/20020
However, this is not yet fixing the problem described originally in the issue.
The presence of "intercept" is apparently managed differently of the regular
processes. That means that those intercepted processors are not wrapped with
the MDC context managements. I am continuing to work on this to see if we can
include those interceptors and have a reliable solution.
> 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)
