activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Davies <rajdav...@gmail.com>
Subject Re: Controlling memory usage for persistent messages
Date Tue, 10 Oct 2006 16:17:08 GMT
keeping messages in memory  pending dispatch will be optional for the  
4.1 GA version of activemq

cheers,

Rob
On 10 Oct 2006, at 13:22, terrytriple wrote:

>
> Afraid I can't help with your question, but I'm looking for an  
> answer to the
> same question !
>
> We are thinking of moving from a JBossMQ solution to ActiveMQ --  
> but having
> the broker block/throw exceptions because it's out of memory due to it
> holding all the messages in memory is a real problem for us.  With our
> existing solution we sometimes have hundreds of thousands of messages
> waiting around.
>
> anyway - looking forward to any reponse to this issue !
>
>
> yaussy wrote:
>>
>> When sending persistent messages (durable topics) to a consumer,  
>> and then
>> the consumer goes away, AMQ 4.x broker consumes memory.  Is there  
>> any way
>> to configure how much it will attempt to keep in memory for  
>> persistent
>> messages??  Seems to me that's the point of having the persistence
>> mechanism (i.e. derby or kaha or Oracle) - capacity at that level  
>> is not
>> an issue.  I can't have the Broker attempting to keep all messages  
>> ready
>> in memory for that failed consumer - it may run out of memory very
>> quickly.
>>
>
> -- 
> View this message in context: http://www.nabble.com/Controlling- 
> memory-usage-for-persistent-messages-tf2382626.html#a6735220
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


Mime
View raw message