You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2008/05/27 17:21:54 UTC

[jira] Resolved: (AMQ-1748) Deadlock when TempUsage limit reached

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

Rob Davies resolved AMQ-1748.
-----------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

Patch applied in SVN  revision 660555

> Deadlock when TempUsage limit reached
> -------------------------------------
>
>                 Key: AMQ-1748
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1748
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0, 5.1.0
>         Environment: Tested on Linux
>            Reporter: Geoff Holden
>            Assignee: Rob Davies
>             Fix For: 5.2.0
>
>         Attachments: TempUsageDeadlock.patch
>
>
> If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
> I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.