[
https://issues.apache.org/jira/browse/ARTEMIS-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670201#comment-16670201
]
ASF subversion and git services commented on ARTEMIS-2155:
----------------------------------------------------------
Commit 3a5d7b2fe797e6e166de4f933015ccc9a38f93b8 in activemq-artemis's branch
refs/heads/2.6.x from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=3a5d7b2 ]
ARTEMIS-2155 disconnect on failure to handle packet
(cherry picked from commit 2a894cbe276b7f3c65b599ee4a262435ba1e687a)
> Failure to handle packet should force consumer to disconnect
> ------------------------------------------------------------
>
> Key: ARTEMIS-2155
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2155
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.6.3
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.7.0, 2.6.4
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
