Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <28889585.2731274788192378.JavaMail.jira@thor>
Date: Tue, 25 May 2010 07:49:52 -0400 (EDT)
From: =?UTF-8?Q?J=C3=B6rn_Kottmann_=28JIRA=29?= <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=3D59=
532#action_59532 ]=20

J=C3=B6rn Kottmann commented on AMQ-2564:
------------------------------------

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

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

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