with <broker persistence="false" /> there is no temp store for the file pending message cursor to use so all messages are retained in memory.
you need to send non persistent messages, producer.setDeliveryMode(NON_PERSISTENT) and enable broker persistence. Then the file cursor will over flow to disk when the systemUsage.memoryLimit is reached. if u don't have controll of the message producers, there is a plugin "forcePersistencyModeBrokerPlugin" that can disable persistence broker side. On 22 April 2013 22:05, SledgeHammer <gro...@firstam.com> wrote: > Trying to set up my ActiveMQ to be non persistent so I can get it as fast as > possible. We don't need to re-queue messages if the queue is restarted. As I > have it right now, it takes 50ms for a 1MB send. When I add > persistance="false" to the broker tag, it drops down to 15ms for a 1MB send. > Issue, of course is that I run out of memory with about 520 messages in the > queue. > > I saw this URL: http://activemq.apache.org/message-cursors.html > > Not sure which set up I need, but I assumed the FileCursor so when the > memory is used up, it swaps out to disk. > > Tried the persistance="false" and: > > <pendingQueuePolicy> > <fileQueueCursor /> > </pendingQueuePolicy> > > But it still died around 520 msgs. Do I need to configure something else? > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Trying-to-set-up-non-persistant-messaging-tp4666127.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
