MDC routeId value is lost after calling a direct route from a camel transacted route

Issue

• We are experiencing issues with the camel.routeId value 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 org.apache.camel.processor.MDCTest.
  The issue goes away if either:

  • direct:b is replaced with direct-vm:b
  • .transacted() is removed from the parent route definition

• In our current routes it appears that converting all direct components into direct-vm components will probably be a workable solution, though we have yet to test this.