We are experiencing issues with the
camel.routeIdvalue is disappearing from the MDC context after calling a direct route.
It seems that this occurs when the direct component is used within a transacted route.
Attached is a test case demonstrating the issue. The case is loosely based on
The issue goes away if either:
direct:bis replaced with
.transacted()is removed from the parent route definition
In our current routes it appears that converting all direct components into
direct-vmcomponents will probably be a workable solution, though we have yet to test this.
- Red Hat JBoss Fuse
- Apache Camel
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.