This looks suspiciously related to a problem that we have been encountering,
but have been unable to narrow down. I don't know if there is an existing
JIRA for this, but if there is, I'd vote for it. Top priority.
Thanks for reporting your insights on this issue.
On Thu, Feb 19, 2009 at 2:57 AM
Hi,
seems like its still a problem in 5.2.0 (fuse 5.2.0.2).
The problem is quite easy to reproduce:
1.Limit the memoryUsage in activemq.xml to -say- 50MB.
2.set producer flow control=false and disable saving messages to disk.
2.Start one producer publishing non-persistent messages with TTL=5sec
To be honest this looks like a bug in the Memory Usage stats :( -
though I believe its fixed in the 5.2 release
thanks,
Rob
On 7 Oct 2008, at 22:38, victorbp wrote:
Thanks Rob!
Now I'm able to receive all the messages using disk spooling, but I
see an
odd behaviour: when the memory is
Thanks Rob!
Now I'm able to receive all the messages using disk spooling, but I see an
odd behaviour: when the memory is full and the broker starts to save the
messages in disk, I can see in JConsole that the MemoryPercentUsage property
increases significantly, much higher than 100% (In some tes
turn off producer flow control - see
http://activemq.apache.org/producer-flow-control.html
cheers,
Rob
On 6 Oct 2008, at 17:33, victorbp wrote:
Hello!
I'm sending non persistent messages to queue and topics (non durable)
through ActiveMQ. I'm trying to use the spooling to disk when memory