You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/04/26 17:04:04 UTC
[jira] [Updated] (CAMEL-11198) OpenTracing trace context should
cope with Hystrix using separate thread
[ https://issues.apache.org/jira/browse/CAMEL-11198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-11198:
--------------------------------
Fix Version/s: 2.19.1
2.20.0
> 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
> Fix For: 2.20.0, 2.19.1
>
>
> 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)