Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <2039471034.1212062880519.JavaMail.jira@brutus>
Date: Thu, 29 May 2008 05:08:00 -0700 (PDT)
From: "Geoff Holden (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQ-1748) Deadlock when TempUsage limit reached
In-Reply-To: <738790667.1211891754381.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Geoff Holden updated AMQ-1748:
------------------------------

    Attachment: missing-file.patch

I had accidentally left a file out of the previous patch.
I've attached a patch for that missing file, which should take care of the unit test regressions.

> 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: missing-file.patch, 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.