activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2564) Pure Master Slave broker hangs when storage limit is reached
Date Tue, 12 Jan 2010 16:23:43 GMT

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

Gary Tully commented on AMQ-2564:
---------------------------------

can you validate that this is still a problem with a current 5.4-SNAPSHOT? There was one deadlock
issue resolve in the past few weeks in the context of being full and not resuming leading
to hung consumers. this was not related to pure master slave however but it may be the difference.

> Pure Master Slave broker hangs when storage limit is reached
> ------------------------------------------------------------
>
>                 Key: AMQ-2564
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2564
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>         Environment: Ubuntu 9.10 Desktop, Java 1.6 (build 1.6.0_16-b01)
>            Reporter: Jörn Kottmann
>            Priority: Minor
>         Attachments: activemq-master.xml, activemq-slave.xml
>
>
> The pure master slave broker hangs when the storage limit is reached and dequeueing messages
from the queue is not possible.
> The behavior can be reproduced with a producer which sends messages to the master broker
until the slave broker writes
>  "INFO | Usage Manager Store is Full. Stopping producer (ID:karkand-51292-1263305705067-0:0:1:1)
to prevent flooding queue://TestQueue. See http://activemq.apache.org/producer-flow-control.html
for more info"
> this message to the console.
> To reproduce the store is full message on the slave broker maybe 2 - 3 attempts are necessary
otherwise
> the messages appears on the console of the master broker.
> Any attempts by a test consumer to dequeue messages fail, it just hangs.
> The following information gather with JMX might be interesting:
> MASTER: StorePercentUsage=99
> SLAVE:    StorePercentUsage=100
> The attributes for the Queue are identical on both 
> brokers.

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