activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BlueFox <bluefox...@gmail.com>
Subject Re: Strange behaviour when broker ran out of disk space
Date Mon, 16 Jun 2008 17:28:40 GMT



BlueFox wrote:
> 
> Hi, I'm encountering a strange behaviour on ActiveMQ 5.1 broker using
> AMQStore for persistence. In my setup, an ActiveMQCPP (2.1.3) producer
> with AUTO_ACKNOWLEDGE is sending persistent message to a queue, which is
> being processed slowly on a consumer using VMTransport on same VM as the
> broker. I don't have any special setting for prefetch or memory/disk limit
> etc.
> 
> When the broker disk space ran out on the broker, the client would receive
> out of disk space error, which is fine. Then the client would treat this
> as a network failure and still keep try to send the message to the broker,
> this repeats for a while as the broker memory usage goes up (!!!) until it
> finally ran out of memory. My question is does it mean that the producer
> need to treat each openwire error differently in order to avoid killing
> the broker? In this case (the broker ran out of disk space), since the
> broker cannot accept any more messages, shouldn't it simply drop any new
> messages coming in until more disk space is available instead of keeping
> all the new messages in the memory?
> 

I found the problem is a part of issue listed in
https://issues.apache.org/activemq/browse/AMQ-724. However, I now encounter
another problem where the persistent message is left in the memory, even
though the disk error should reject the message....
-- 
View this message in context: http://www.nabble.com/Strange-behaviour-when-broker-ran-out-of-disk-space-tp17843784p17869391.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message