[
https://issues.apache.org/jira/browse/AMQ-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363114#comment-15363114
]
ASF subversion and git services commented on AMQ-6305:
------------------------------------------------------
Commit 508c12d9487ad653f05806be7a492e4bd870522b in activemq's branch
refs/heads/activemq-5.13.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=508c12d ]
https://issues.apache.org/jira/browse/AMQ-6305
Add test and supporting enhancements to the JUnit module to allow for
easy repetition of tests that don't always fail reliably
(cherry picked from commit 6ae169e2755257b1e8e5068473bdb3156160790d)
> 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)
