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

Conflict with Netty TCP + Resilience4J circuit breaker

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.7.4, 3.10.0
    • 3.7.5, 3.11.0
    • camel-netty
    • None
    • Advanced

    Description

      My team has found what we believe is a conflict between the Netty TCP producer and the Resilience4J circuit breaker, under specific circumstances.

      When the Netty TCP client encounters an error while writing to the server (for us, usually a broken pipe exception), if it is inside a circuit breaker, the route will hang indefinitely.

      Discussion on Zulip: Conflict with Netty TCP + Resilience4J circuit breaker

      A zipped version of the complete test project is attached.  It should allow you to reproduce the issue.

      By running BrokeTCPServer.main(), and then invoking NettyTest.testNettyCircuitBreaker(), you should see that of the two messages we push into the queue, only one is processed. Only one connection is initiated to the BrokeTCPServer.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            davsclaus Claus Ibsen
            Morgan L Morgan L
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment