You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2009/01/07 09:12:06 UTC

[jira] Resolved: (AMQ-2053) AMQMessageStore.flushLatch can apparently get stuck

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

David Jencks resolved AMQ-2053.
-------------------------------

    Resolution: Fixed

New methods introduced in rev 732259.

> 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.