[jira] Updated: (AMQ-2564) Pure Master Slave broker hangs when storage limit is reached

["Jörn Kottmann (JIRA)" <ji...@apache.org>]

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

Jörn Kottmann updated AMQ-2564:
-------------------------------

    Attachment: activemq-slave.xml
                activemq-master.xml

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