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 2018/03/09 12:42:00 UTC

[jira] [Resolved] (AMQ-6924) StoreDurableSubscriberCursor does not timeout properly on non-persistent message send

     [ https://issues.apache.org/jira/browse/AMQ-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher L. Shannon resolved AMQ-6924.
-----------------------------------------
    Resolution: Fixed

> 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)