rajdavies wrote:
>
> Store usage controls the maximum size of the AMQMessage Store
> TempUsage is the maximum size of the store used for non-persistent
> messages that may optionally overflow from memory awaiting dispatch
> MemoryUsage is the maximum amount of memory the broker will use
>
> c
I think I've come across another case with ver5.0 (released) where the memory
used by the linkedlist pagedInMessages can result in broker memory bloat for
large messages. The case involves a very slow consumer, wherein the messages
sent by the producer are kept in the linkedlist. The reason for th
Thanks :)
--
View this message in context:
http://www.nabble.com/ActiveMQ-ver5.0-number-of-paged-in-messages-tp14860957s2354p14955497.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
After further investigation, it would appear that in the following code
snippet...
531public void acknowledge(ConnectionContext context, Subscription
sub, MessageAck ack, MessageReference node) throws IOException {
532if (store != null && node.isPersistent()) {
533
Hi,
I'm currently using ActiveMQ ver5.0 with persistence turned on, and running
1 broker, 1 producer, and 1 consumer. I'm using a queue to send and receive
non-transactional ObjectMessages. The objects in the messages are several
megs, hence, I have setUseCompression(true).
The problem I'm enco
