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 16:59:04 GMT

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

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

GitHub user objectiser opened a pull request:

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

    CAMEL-11198 Fix issue with propagating the trace context when using h…

    …ystrix

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/objectiser/camel CAMEL-11198

Alternatively you can review and apply these changes as the patch at:

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1662
    
----
commit 667c38992dad2475866bfdd9d492f4df382c5a9e
Author: Gary Brown <gary@brownuk.com>
Date:   2017-04-26T16:37:52Z

    CAMEL-11198 Fix issue with propagating the trace context when using hystrix

----


> 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