[
https://issues.apache.org/jira/browse/AMQ-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024603#comment-16024603
]
ASF subversion and git services commented on AMQ-6687:
------------------------------------------------------
Commit 25f112c5c9a843f162296ad38eb79be47183e0be in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=25f112c ]
[AMQ-6687] ensure transacted sends blocked on pfc do not resume after tx
completion. AMQ-4467 refine the fix such that PFC kicks in such that the cache
will accept messsages that push it over it's limit while it is still under the
limit
> destination memory usage incorrect after flow control (PFC) sendTimeout and
> rollback
> ------------------------------------------------------------------------------------
>
> Key: AMQ-6687
> URL: https://issues.apache.org/jira/browse/AMQ-6687
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.14.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.15.0
>
>
> When using PFC, to block a producer on a memory limit and using a sendTimeout
> to error out after some timeout. If there is a send transaction the send
> completes in error even though the transaction has completed once usage
> allows.
> Leaving a dangling send that shows up in the memory usage.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
