[
https://issues.apache.org/jira/browse/AMQ-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880194#comment-16880194
]
ASF subversion and git services commented on AMQ-7234:
------------------------------------------------------
Commit ede4dbc8649792628b1135db9cdf9b06fd6844df in activemq's branch
refs/heads/activemq-5.15.x from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=ede4dbc ]
AMQ-7234 - fix up memory usage wait timeout such that topic pfc in a
transaction can see connection context state changes, fix and test
(cherry picked from commit de3f77063fa579159184d23ac98df97e80d63327)
> Topic flow control with messages in a transaction can loop forever waiting
> for usage
> ------------------------------------------------------------------------------------
>
> Key: AMQ-7234
> URL: https://issues.apache.org/jira/browse/AMQ-7234
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.16.0
>
>
> The memory usage wait(timeout > 0) does not respect the timeout. Topic pfc
> loops on that wait to check the connection context, but it never gets to
> check the status and stays hung even when jmx is used to kill the connection.
> If the topic producer uses alwaysSendSync it avoids this code path and can be
> closes via JMX and the rollback will release resources as expected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
