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 2016/08/02 11:56:20 UTC

[jira] [Updated] (AMQ-6056) Refactor non-persistent limits in terms of the temporary store usage

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

Christopher L. Shannon updated AMQ-6056:
----------------------------------------
    Fix Version/s:     (was: 5.14.0)
                   5.15.0

> Refactor non-persistent limits in terms of the temporary store usage
> --------------------------------------------------------------------
>
>                 Key: AMQ-6056
>                 URL: https://issues.apache.org/jira/browse/AMQ-6056
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.12.1
>            Reporter: Christopher L. Shannon
>             Fix For: 5.15.0
>
>
> Refactor the limits used for tracking of non-persistent messages so that the limit of the temporary store usage is taken into account instead of just the memory usage limit as the messages in memory can be higher than available temporary storage.  This scenario could cause deadlocks such as the scenario in AMQ-5712.  
> The fix in AMQ-5712 works around this by using a timeout when trying to add a message to a Queue to prevent a deadlock but this is just a work around and the underlying cause should be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)