Using ActiveMQ fileQueueCursor and the temp store without enabling persistence -
i'm using activemq 5.7.0 , want filequeuecursor spill temp store if queue destination reaches memory threshold. don't want enable persistence.
i've configured destinationpolicy:
<destinationpolicy> <policymap> <policyentries> <policyentry queue=">"> <pendingqueuepolicy> <filequeuecursor /> </pendingqueuepolicy> </policyentry> </policyentries> </policymap> </destinationpolicy>
i've configured systemusage low memoryusage testing:
<systemusage> <systemusage> <memoryusage> <memoryusage limit="5 mb" /> </memoryusage> <tempusage> <tempusage limit="32 mb" /> </tempusage> </systemusage> </systemusage>
i have code running in debugger insert messages queue. while running can see messages increased memory usage:
2013-may-09 17:40:12.963 pdt debug [activemq transport: tcp:///127.0.0.1:63223@61616] [org.apache.activemq.usage.usage:fireevent] [usage.java:245] [] [] [] - default:memory:queue://testreq:memory: usage change from: 69% of available memory, to: 70% of available memory
i've noticed amq's filependingmessagecursor.flushtodisk() called @ around 70% memory usage because 'store' member null code not executed.
when enable persistence store not null , flushtodisk() completes.
is possible set temporary store without enabling persistence?
Comments
Post a Comment