Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-11198

OpenTracing trace context should cope with Hystrix using separate thread

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.19.0
    • Fix Version/s: 2.19.0, 2.20.0
    • Component/s: camel-hystrix
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      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".

        Attachments

          Activity
          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              garybrown Gary Brown

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment