You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Tomáš Martinec (JIRA)" <ji...@apache.org> on 2012/12/18 14:34:12 UTC

[jira] [Comment Edited] (AMQ-4230) Activemq hangs when temp storage is used

    [ https://issues.apache.org/jira/browse/AMQ-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534871#comment-13534871 ] 

Tomáš Martinec edited comment on AMQ-4230 at 12/18/12 1:34 PM:
---------------------------------------------------------------

Patch unsynchronizing-cursors.diff required after applying making-cursors-RWlock-aware.diff.
                
      was (Author: tomas.martinec@d3s.mff.cuni.cz):
    Required after applying making-cursors-RWlock-aware.diff
                  
> Activemq hangs when temp storage is used
> ----------------------------------------
>
>                 Key: AMQ-4230
>                 URL: https://issues.apache.org/jira/browse/AMQ-4230
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2, 5.7.0
>         Environment: fedora15; ubuntu 12.10; debian; probably platform independent
>            Reporter: Tomáš Martinec
>              Labels: cursors,, deadlock,, temp-storage
>         Attachments: extending.kahadb.diff, making-cursors-RWlock-aware.diff, unsynchronizing-cursors.diff
>
>
> The full story is user forum under title:
> Activemq 5.4.2 hangs when the temp disk usage is used
> On the line 219 of http://svn.apache.org/viewvc/activemq/tags/activemq-5.4.2/activemq-core/src/main/java/org/apache/activemq/broker/region/cursors/FilePendingMessageCursor.java?view=markup I unlocked the messagesLock that was created in the queue. I have done that, because the writer thread waits for free space, but the consumers are locked waiting until the writer thread releases the lock.
> My fixing approach was making the cursors aware of the RW lock. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira