[
https://issues.apache.org/jira/browse/CAMEL-11198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-11198.
---------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: (was: 2.19.1)
2.19.0
We re-cut the release
> OpenTracing trace context should cope with Hystrix using separate thread
> ------------------------------------------------------------------------
>
> Key: CAMEL-11198
> URL: https://issues.apache.org/jira/browse/CAMEL-11198
> Project: Camel
> Issue Type: Bug
> Components: camel-hystrix
> Affects Versions: 2.19.0
> Reporter: Gary Brown
> Assignee: Claus Ibsen
> Fix For: 2.20.0, 2.19.0
>
>
> 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".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
