become quite full
>>>>> of
>>>>> pending messages.
>>>>> The result of slow consumers with producerFlowControl disabled is a
>>>>> constant
>>>>> increase of the memory with the number of pending messages.
>>>>
mq.broker.region.Queue related to our full queue has a
>>>> reference to all pending messages.
>>>> Each org.apache.activemq.broker.region.IndirectMessageReference object
>>>> linked to queue contains a reference to the original
>>>> org.apache.activemq.com
ject
>>> linked to queue contains a reference to the original
>>> org.apache.activemq.command.ActiveMQTextMessage object with all content
>>> (jms
>>> message body).
>>> What is the reason of caching all the pending object when we work with
>>> pers
caching all the pending object when we work with
>> persistent messages?
>> There is an option we can set to avoid this behaviour?
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Persistent-messages-cache-causes-OutOfMemory-tp2910p2910.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
veMQTextMessage object with all content (jms
> message body).
> What is the reason of caching all the pending object when we work with
> persistent messages?
> There is an option we can set to avoid this behaviour?
>
>
> --
> View this message in context:
> http://old.nabble.co
://old.nabble.com/Persistent-messages-cache-causes-OutOfMemory-tp2910p2910.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
