Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1535864734.1231314965534.JavaMail.jira@brutus>
Date: Tue, 6 Jan 2009 23:56:05 -0800 (PST)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2053) AMQMessageStore.flushLatch can
 apparently get stuck
In-Reply-To: <1702341665.1231033325414.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-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48519#action_48519 ] 

David Jencks commented on AMQ-2053:
-----------------------------------

Problem is that the AMQMessageStore is closed but not removed from the cache inside the PersistenceAdapter.  Next time a Queue (or Topic) is created it gets the stopped and unusable message store from the cache.

After chatting with Hiram on the dev list I think introducing methods to remove the message store from the persistence adapter is the best way forward.

Looking at svn history this problem was introduced in the fix for AMQ-1842, rev 729939, where the calls to stop the MessageStore were introduced.

> AMQMessageStore.flushLatch can apparently get stuck
> ---------------------------------------------------
>
>                 Key: AMQ-2053
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2053
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 5.3.0
>
>
> A couple hours into the tck I see everything freeze.  Looking at the threads there are a lot of waits on Queue.dispatchLock in addSubscription but one thread made it through to AMQMessageStore and is waiting at line 316 in flush on the countdown latch.
> Only problem I can see causing this so far is the countdown in asyncWrite not being in a finally block.  I don't see any exceptions in the log.... so not sure yet.

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