Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1769454146.121263313423725.JavaMail.jira@brutus.apache.org>
Date: Tue, 12 Jan 2010 16:23:43 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2564) Pure Master Slave broker hangs when
 storage limit is reached
In-Reply-To: <830893697.61263306823490.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/activemq/browse/AMQ-2564?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D56=
872#action_56872 ]=20

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 o=
f being full and not resuming leading to hung consumers. this was not relat=
ed 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=C3=B6rn 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 th=
e 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://a=
ctivemq.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 at=
tempts 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=3D99
> SLAVE:    StorePercentUsage=3D100
> The attributes for the Queue are identical on both=20
> brokers.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.