[
https://issues.apache.org/jira/browse/AMQ-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392827#comment-16392827
]
ASF subversion and git services commented on AMQ-6924:
------------------------------------------------------
Commit 5e2adc0ed7dfe2e827bdef878f1c8cde12ff5773 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=5e2adc0 ]
AMQ-6924 - Fix StoreDurableSubscriberCursor non-persistent message add
StoreDurableSubscriberCursor now properly uses a timeout value when
attempting to add to the temporary store for non-persistent messages to
prevent an indefinite wait on free space
> StoreDurableSubscriberCursor does not timeout properly on non-persistent
> message send
> -------------------------------------------------------------------------------------
>
> Key: AMQ-6924
> URL: https://issues.apache.org/jira/browse/AMQ-6924
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.15.3
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 5.16.0, 5.15.4
>
>
> I found an issue today on a broker when the temporary store was full and a
> non-persistent message was trying to be added to a durable subscription.
> Analysis showed that the broker was stuck in a loop trying to add the
> non-persistent message to the temporary store because the maxWaitTime value
> is not properly used inside of StoreDurableSubscriberCursor. Instead of
> honoring a timeout value and failing, the waitForSpace() method call on the
> temporary store was stuck in a loop waiting indefinitely for free space.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
