camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11198) OpenTracing trace context should cope with Hystrix using separate thread
Date Wed, 26 Apr 2017 17:03:04 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-11198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985146#comment-15985146
] 

ASF GitHub Bot commented on CAMEL-11198:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/camel/pull/1662


> 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)

Mime
View raw message