Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <26711191.post@talk.nabble.com>
Date: Wed, 9 Dec 2009 06:35:22 -0800 (PST)
From: Duro <durokuruc@zoznam.sk>
To: users@activemq.apache.org
Subject: Re: Memory limit reached on persistent queue
In-Reply-To: <3a73c17c0912090536o67d3dac4uaba017b1ad1511f6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <26709801.post@talk.nabble.com>
 <3a73c17c0912090536o67d3dac4uaba017b1ad1511f6@mail.gmail.com>


no, both versions behave as expected.

Gary Tully wrote:
> 
> Does the problem persist with trunk (5.4-SNAPSHOT) or on the 5.3.1-branch
> (5.3.1-SNAPSHOT).
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/
> 
> 2009/12/9 Duro <durokuruc@zoznam.sk>
> 
>>
>> Hi,
>> I'am using ActiveMQ 5.3 with kahaPersistenceAdapter my test case is:
>> - slow consumer(s)
>> - fast producer
>> - persistent queue
>> - producerFlowControl="true"
>> - Win XP (Sles10)
>>
>> after couple thousand of massages stored massages i can find following
>> massge on console:
>>
>> INFO | Usage Manager memory limit reached on queue://slowConsumerDest.
>> Producers will be throttled to the rate at which messages are removed
>> from
>> this destination to prevent flooding it. See
>> http://activemq.apache.org/producer-flow-control.html for more info
>>
>> -in jconsole i see that CursorPercentUsage reached value 100.
>> from this point no more messages are persisted to disc and producer si
>> sending only as fast as consumer(s) are receiving.
>>
>> My question is why no more messages are stored when i'm using persistent
>> messaging?
>>
>> I've try same configuration on ActiveMQ 5.3 snapshot (rev. number 747951)
>> -
>> CursorPercentUsage reached 70 and incomming messages were stored as i've
>> expected.
>> This mechanism works with Amq 5.3 in case amqPersistenceAdapter is used,
>> for
>> kahaPersistenceAdapter when topic with durable subscriber used instead of
>> queue and for queue in case it has no consumers.
>> Using of kahadb is not an option in my case while handling of persistent
>> massages is several times slower.
>>
>> Regards,
>> Juraj
>>
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Memory-limit-reached-on-persistent-queue-tp26709801p26709801.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> http://blog.garytully.com
> 
> Open Source Integration
> http://fusesource.com
> 
> 

-- 
View this message in context: http://old.nabble.com/Memory-limit-reached-on-persistent-queue-tp26709801p26711191.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.