Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.217.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1343645487756-4654530.post@n4.nabble.com>
References: <1343642533893-4654526.post@n4.nabble.com>
	<CAH+vQmPLDd3eoeMt0DPYRfcynKfnKLv1_MuZTWewRinZuYaaYA@mail.gmail.com>
	<1343645487756-4654530.post@n4.nabble.com>
Date: Mon, 30 Jul 2012 12:05:03 +0100
Message-ID: 
 <CAH+vQmOJCExf2nmv9M5UL_qq7zWCx9D=FURaU7ygx9M+iT3y+Q@mail.gmail.com>
Subject: Re: Lost non-persistent messages
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1

There should be no message loss, if the memory limit is reached or
paging to disk is enabled and the temp store is full, blocking
should/will occur.

The only cause for message loss with non persistent messages on a
queue is if the broker is restarted with message pending for dispatch.

On 30 July 2012 11:51, Tom Martinec <martinec@d3s.mff.cuni.cz> wrote:
>
> gtully wrote
>>
>> iirc that is better in 5.6
>>
>
> well, have not tried 5.6, but the same problem is likely to be there too,
> because the code in tryAddMessageLast looks the same:
>
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/cursors/FilePendingMessageCursor.java?revision=1202153&view=markup
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/cursors/FilePendingMessageCursor.java?revision=1202153&view=markup
>
> Anyway, should the producer be blocked?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Lost-non-persistent-messages-tp4654526p4654530.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.


-- 
http://fusesource.com
http://blog.garytully.com