[
https://issues.apache.org/jira/browse/CAMEL-22717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040578#comment-18040578
]
Claus Ibsen commented on CAMEL-22717:
-------------------------------------
Yeah that part of interceptor is not support in this use-case. The
InterceptStrategy is static as part of when the route graph is being assembled.
You can try an experiment to wrap this code
[https://github.com/apache/camel/blob/4a95021560ba1f59a2d929ba2d620eaee6d0e365/core/camel-core-reifier/src/main/java/org/apache/camel/reifier/InterceptSendToEndpointReifier.java#L78]
And wrap that Pipeline via the MDCProcessorsInterceptStrategy just to give it a
test and see if that then ensures the MDC is set/unset. That gives us a clue if
we can make this possible in the future and then come up with a nicer 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)
