thanks for reporting back and closing the loop on this one :-)
On 28 August 2012 22:55, Jeremy Levy wrote:
> I was able to solve both issues, It wasn't clear to me that
> memoryLimit="2mb" was the corresponding setting on the queue policy in
> regards to the memory limit threshold before spooling
I was able to solve both issues, It wasn't clear to me that
memoryLimit="2mb" was the corresponding setting on the queue policy in
regards to the memory limit threshold before spooling to disk. Therefore I
think it was starting with the disk right away. After changing that to
something reasonably
Also, it doesn't seem as though fileQueueCursor is working as described in
many places in the documentation:
http://activemq.apache.org/message-cursors.html says:
"When memory in the broker reaches its limit, it can page messages to
temporary files on disk. "
http://activemq.apache.org/javalangou
Hi Gary-
Thanks for the quick response, as I read that it's fixed in 5.6.0, however
I'm using 5.6.0... I'm only seeing the directory cleaned up during a
restart.
Jeremy
On Tue, Aug 28, 2012 at 11:03 AM, Gary Tully wrote:
> If you are sending non persistent messages see
> https://issues.apache.
If you are sending non persistent messages see
https://issues.apache.org/jira/browse/AMQ-3780
On 28 August 2012 15:44, Jeremy Levy wrote:
> When using fileQueueCursor, as I understand it the data is written to the
> tmp-storage directory. When does this directory get cleaned up. For
> example I
