[
https://issues.apache.org/jira/browse/ARTEMIS-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100306#comment-16100306
]
clebert suconic commented on ARTEMIS-1283:
------------------------------------------
open/closed to fix assignee
> AMQP Drain of a link encounters unexpected response delay
> ---------------------------------------------------------
>
> Key: ARTEMIS-1283
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1283
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.1.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 2.2.0
>
>
> When an AMQP attempts to drain a link the broker can take a inordinate amount
> of time to respond that the link is drained, especially if there's no
> messages to send. This happens because the action that attempts to force
> delivery is signaled of completion via a callback and the update to proton is
> made but no flush of the connection state is done.
> As a side not the drained call to the link is done outside the connection
> lock which is unsafe.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
