[
https://issues.apache.org/jira/browse/ARTEMIS-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-2155:
------------------------------------
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. (was: 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 update it's credits and therefore doesn't ask for
additional credits. The client should disconnect consistently when it has
problems decoding a packet.)
> 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
>
> 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)
