activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörn Kottmann (JIRA) <>
Subject [jira] Commented: (AMQ-2564) Pure Master Slave broker hangs when storage limit is reached
Date Tue, 25 May 2010 11:49:52 GMT


Jörn Kottmann commented on AMQ-2564:

Finding the right higher value on the slave seems to be tricky, since it depends on the message
size which is usually dynamic,
which means that depending on the configuration the broker could work for quite some time
and then fail suddenly when a bunch of bigger messages is received (which might happen, depending
on the application).

Users which choose a PureMasterSlave configurtion are really focused on stability.
For this particular issue the slave should maybe disable the flow control completely when
the master is healthy, 
what do you think Gary ?

> Pure Master Slave broker hangs when storage limit is reached
> ------------------------------------------------------------
>                 Key: AMQ-2564
>                 URL:
>             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
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
> 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.

View raw message