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 <marti...@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
