Thanks for replies...
Any message actually never got lost. What I saw was just a few confusing
observations:)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Lost-non-persistent-messages-tp4654526p4654718.html
Sent from the ActiveMQ - User mailing list archive at Nabbl
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
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/FilePe
iirc that is better in 5.6
On 30 July 2012 11:02, Tom Martinec wrote:
> Hello,
>
> I observed a different behavior of activemq 5.4.2 when sending
> non-persistent messages to different cursors. The message producer is
> blocked when the cursor is set to VMCursor and the destination queue is
> ful
