Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-2155

Failure to handle packet should force consumer to disconnect

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.6.3
    • 2.6.4, 2.7.0
    • None
    • None

    Description

      Usually when a core client fails to decode an incoming buffer it logs the failure and disconnects. However, there are a few situations where the failure is logged, but the client doesn't disconnect. This can lead to client starvation situations involving flow control where the broker thinks the client has successfully received the packet but the client doesn't ask for additional credits. The client should disconnect consistently when it has problems decoding a packet.

      Attachments

        Activity

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

          People

            jbertram Justin Bertram
            jbertram Justin Bertram
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment