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, 25 May 2010 12:04:52 GMT

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

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

Agree, this is not ideal, but it is not just flow control, it is any memory limit because
the default behavior is to block a send if the memory limit is reached. So the slave should
be configured with large memory limits or left unbounded.

> 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
>            Assignee: Gary Tully
>            Priority: Minor
>             Fix For: 5.4.0
>
>         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