activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoff Holden (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-1748) Deadlock when TempUsage limit reached
Date Tue, 27 May 2008 12:35:54 GMT
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.1.0, 5.0.0
         Environment: Tested on Linux
            Reporter: Geoff Holden
         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.


Mime
View raw message