[CAMEL-11198] OpenTracing trace context should cope with Hystrix using separate thread

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.19.0
• Fix Version/s: 2.19.0, 2.20.0
• Component/s: camel-hystrix
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Gary Brown
• Created: 25/Apr/17 14:50
• Updated: 23/May/17 12:23
• Resolved: 23/May/17 12:23

Description

When using OpenTracing with Hystrix, the default Hystrix configuration uses a separate thread for the outbound request.

Currently the trace context from the route is not carried across to this new thread, causing the outbound request to be recorded in a separate trace instance.

Need to ensure that the trace context is carried to the new thread/exchange.

As a workaround, the Hystrix configuration property executionIsolationStrategy should be set to "SEMAPHORE".

Issue Links

• links to: GitHub Pull Request #1662