You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/07/05 18:34:11 UTC

[jira] [Commented] (AMQ-6305) AMQP: Drain requests can go unaswered in certain cases.

    [ https://issues.apache.org/jira/browse/AMQ-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362962#comment-15362962 ] 

Christopher L. Shannon commented on AMQ-6305:
---------------------------------------------

[~tabish121],

Should these commits be backported to 5.13.4? (I'm assuming so because you marked this as 5.13.4 for the fix version)  I ask because the current 5.13.x branch doesn't build right now.  Looks like there is a compilation error from a missing method in the JmsClientTestSupport class that was added in one of these commits.

> AMQP: Drain requests can go unaswered in certain cases.
> -------------------------------------------------------
>
>                 Key: AMQ-6305
>                 URL: https://issues.apache.org/jira/browse/AMQ-6305
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 5.13.0, 5.13.1, 5.13.2, 5.13.3
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.14.0, 5.13.4
>
>
> In some cases when an AMQP client issues a flow that indicates a request to drain off credit or pull some amount of messages the broker can fail to respond due to interactions between the via of credit and other factors like prefetch extension which can leave a message queued on link and not be accounted for.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)