You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Gary Brown (JIRA)" <ji...@apache.org> on 2017/04/25 14:51:04 UTC
[jira] [Created] (CAMEL-11198) OpenTracing trace context should
cope with Hystrix using separate thread
Gary Brown created CAMEL-11198:
----------------------------------
Summary: 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
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)