You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/08/31 16:38:01 UTC
[jira] [Resolved] (ARTEMIS-1315) Client disconnection may cause
consumer to hang
[ https://issues.apache.org/jira/browse/ARTEMIS-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-1315.
-------------------------------------
Resolution: Fixed
> Client disconnection may cause consumer to hang
> -----------------------------------------------
>
> Key: ARTEMIS-1315
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1315
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.5.5, 2.2.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 1.5.6, 2.3.0
>
>
> When calling a consumer to receive message with a timeout (receive(long timeout), if the consumer's buffer is empty, it sends a 'forced delivery' then
> waiting forever, expecting the server sends back a 'forced delivery" message if the queue is empty.
> It the connection is disconnected as the arrived 'forced delivery' message is corrupted, this 'forced delivery' message never gets to consumer. After the session
> is reconnected, the consumer never knows that and stays waiting.
> To fix that we can send a 'forced delivery' to server right after the session is reconnected.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)