You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by yaussy <ya...@cboe.com> on 2006/10/04 16:20:51 UTC
Controlling memory usage for persistent messages
When sending persistent messages (durable topics) to a consumer, and then the
consumer goes away, AMQ 4.x broker consumes memory. Is there any way to
configure how much it will attempt to keep in memory for persistent
messages?? Seems to me that's the point of having the persistence mechanism
(i.e. derby or kaha or Oracle) - capacity at that level is not an issue. I
can't have the Broker attempting to keep all messages ready in memory for
that failed consumer - it may run out of memory very quickly.
--
View this message in context: http://www.nabble.com/Controlling-memory-usage-for-persistent-messages-tf2382626.html#a6640467
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Controlling memory usage for persistent messages
Posted by yaussy <ya...@cboe.com>.
Rob,
I've downloaded 4.1, but this problem is still there. I hope this will be
fixed, as I can't see why you'd want to persist to storage, but also to
memory. This is a very big problem for us.
yaussy wrote:
>
> OK, thanks.
>
>
> rajdavies wrote:
>>
>> Its not available from SVN yet - but should be next week
>>
>> cheers,
>>
>> Rob
>> On 12 Oct 2006, at 21:08, yaussy wrote:
>>
>>>
>>> Thanks, Rob. Is this in the current 4.1 build? I will try it out...
>>>
>>>
>>> rajdavies wrote:
>>>>
>>>> keeping messages in memory pending dispatch will be optional for the
>>>> 4.1 GA version of activemq
>>>>
>>>> cheers,
>>>>
>>>> Rob
>>>> On 10 Oct 2006, at 13:22, terrytriple wrote:
>>>>
>>>>>
>>>>> Afraid I can't help with your question, but I'm looking for an
>>>>> answer to the
>>>>> same question !
>>>>>
>>>>> We are thinking of moving from a JBossMQ solution to ActiveMQ --
>>>>> but having
>>>>> the broker block/throw exceptions because it's out of memory due
>>>>> to it
>>>>> holding all the messages in memory is a real problem for us.
>>>>> With our
>>>>> existing solution we sometimes have hundreds of thousands of
>>>>> messages
>>>>> waiting around.
>>>>>
>>>>> anyway - looking forward to any reponse to this issue !
>>>>>
>>>>>
>>>>> yaussy wrote:
>>>>>>
>>>>>> When sending persistent messages (durable topics) to a consumer,
>>>>>> and then
>>>>>> the consumer goes away, AMQ 4.x broker consumes memory. Is there
>>>>>> any way
>>>>>> to configure how much it will attempt to keep in memory for
>>>>>> persistent
>>>>>> messages?? Seems to me that's the point of having the persistence
>>>>>> mechanism (i.e. derby or kaha or Oracle) - capacity at that level
>>>>>> is not
>>>>>> an issue. I can't have the Broker attempting to keep all messages
>>>>>> ready
>>>>>> in memory for that failed consumer - it may run out of memory very
>>>>>> quickly.
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context: http://www.nabble.com/Controlling-
>>>>> memory-usage-for-persistent-messages-tf2382626.html#a6735220
>>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context: http://www.nabble.com/Controlling-
>>> memory-usage-for-persistent-messages-tf2382626.html#a6783729
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Controlling-memory-usage-for-persistent-messages-tf2382626.html#a7688484
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Controlling memory usage for persistent messages
Posted by yaussy <ya...@cboe.com>.
OK, thanks.
rajdavies wrote:
>
> Its not available from SVN yet - but should be next week
>
> cheers,
>
> Rob
> On 12 Oct 2006, at 21:08, yaussy wrote:
>
>>
>> Thanks, Rob. Is this in the current 4.1 build? I will try it out...
>>
>>
>> rajdavies wrote:
>>>
>>> keeping messages in memory pending dispatch will be optional for the
>>> 4.1 GA version of activemq
>>>
>>> cheers,
>>>
>>> Rob
>>> On 10 Oct 2006, at 13:22, terrytriple wrote:
>>>
>>>>
>>>> Afraid I can't help with your question, but I'm looking for an
>>>> answer to the
>>>> same question !
>>>>
>>>> We are thinking of moving from a JBossMQ solution to ActiveMQ --
>>>> but having
>>>> the broker block/throw exceptions because it's out of memory due
>>>> to it
>>>> holding all the messages in memory is a real problem for us.
>>>> With our
>>>> existing solution we sometimes have hundreds of thousands of
>>>> messages
>>>> waiting around.
>>>>
>>>> anyway - looking forward to any reponse to this issue !
>>>>
>>>>
>>>> yaussy wrote:
>>>>>
>>>>> When sending persistent messages (durable topics) to a consumer,
>>>>> and then
>>>>> the consumer goes away, AMQ 4.x broker consumes memory. Is there
>>>>> any way
>>>>> to configure how much it will attempt to keep in memory for
>>>>> persistent
>>>>> messages?? Seems to me that's the point of having the persistence
>>>>> mechanism (i.e. derby or kaha or Oracle) - capacity at that level
>>>>> is not
>>>>> an issue. I can't have the Broker attempting to keep all messages
>>>>> ready
>>>>> in memory for that failed consumer - it may run out of memory very
>>>>> quickly.
>>>>>
>>>>
>>>> --
>>>> View this message in context: http://www.nabble.com/Controlling-
>>>> memory-usage-for-persistent-messages-tf2382626.html#a6735220
>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>>
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Controlling-
>> memory-usage-for-persistent-messages-tf2382626.html#a6783729
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Controlling-memory-usage-for-persistent-messages-tf2382626.html#a6783911
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Controlling memory usage for persistent messages
Posted by Rob Davies <ra...@gmail.com>.
Its not available from SVN yet - but should be next week
cheers,
Rob
On 12 Oct 2006, at 21:08, yaussy wrote:
>
> Thanks, Rob. Is this in the current 4.1 build? I will try it out...
>
>
> rajdavies wrote:
>>
>> keeping messages in memory pending dispatch will be optional for the
>> 4.1 GA version of activemq
>>
>> cheers,
>>
>> Rob
>> On 10 Oct 2006, at 13:22, terrytriple wrote:
>>
>>>
>>> Afraid I can't help with your question, but I'm looking for an
>>> answer to the
>>> same question !
>>>
>>> We are thinking of moving from a JBossMQ solution to ActiveMQ --
>>> but having
>>> the broker block/throw exceptions because it's out of memory due
>>> to it
>>> holding all the messages in memory is a real problem for us.
>>> With our
>>> existing solution we sometimes have hundreds of thousands of
>>> messages
>>> waiting around.
>>>
>>> anyway - looking forward to any reponse to this issue !
>>>
>>>
>>> yaussy wrote:
>>>>
>>>> When sending persistent messages (durable topics) to a consumer,
>>>> and then
>>>> the consumer goes away, AMQ 4.x broker consumes memory. Is there
>>>> any way
>>>> to configure how much it will attempt to keep in memory for
>>>> persistent
>>>> messages?? Seems to me that's the point of having the persistence
>>>> mechanism (i.e. derby or kaha or Oracle) - capacity at that level
>>>> is not
>>>> an issue. I can't have the Broker attempting to keep all messages
>>>> ready
>>>> in memory for that failed consumer - it may run out of memory very
>>>> quickly.
>>>>
>>>
>>> --
>>> View this message in context: http://www.nabble.com/Controlling-
>>> memory-usage-for-persistent-messages-tf2382626.html#a6735220
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Controlling-
> memory-usage-for-persistent-messages-tf2382626.html#a6783729
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: Controlling memory usage for persistent messages
Posted by yaussy <ya...@cboe.com>.
Thanks, Rob. Is this in the current 4.1 build? I will try it out...
rajdavies wrote:
>
> keeping messages in memory pending dispatch will be optional for the
> 4.1 GA version of activemq
>
> cheers,
>
> Rob
> On 10 Oct 2006, at 13:22, terrytriple wrote:
>
>>
>> Afraid I can't help with your question, but I'm looking for an
>> answer to the
>> same question !
>>
>> We are thinking of moving from a JBossMQ solution to ActiveMQ --
>> but having
>> the broker block/throw exceptions because it's out of memory due to it
>> holding all the messages in memory is a real problem for us. With our
>> existing solution we sometimes have hundreds of thousands of messages
>> waiting around.
>>
>> anyway - looking forward to any reponse to this issue !
>>
>>
>> yaussy wrote:
>>>
>>> When sending persistent messages (durable topics) to a consumer,
>>> and then
>>> the consumer goes away, AMQ 4.x broker consumes memory. Is there
>>> any way
>>> to configure how much it will attempt to keep in memory for
>>> persistent
>>> messages?? Seems to me that's the point of having the persistence
>>> mechanism (i.e. derby or kaha or Oracle) - capacity at that level
>>> is not
>>> an issue. I can't have the Broker attempting to keep all messages
>>> ready
>>> in memory for that failed consumer - it may run out of memory very
>>> quickly.
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Controlling-
>> memory-usage-for-persistent-messages-tf2382626.html#a6735220
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Controlling-memory-usage-for-persistent-messages-tf2382626.html#a6783729
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Controlling memory usage for persistent messages
Posted by Rob Davies <ra...@gmail.com>.
keeping messages in memory pending dispatch will be optional for the
4.1 GA version of activemq
cheers,
Rob
On 10 Oct 2006, at 13:22, terrytriple wrote:
>
> Afraid I can't help with your question, but I'm looking for an
> answer to the
> same question !
>
> We are thinking of moving from a JBossMQ solution to ActiveMQ --
> but having
> the broker block/throw exceptions because it's out of memory due to it
> holding all the messages in memory is a real problem for us. With our
> existing solution we sometimes have hundreds of thousands of messages
> waiting around.
>
> anyway - looking forward to any reponse to this issue !
>
>
> yaussy wrote:
>>
>> When sending persistent messages (durable topics) to a consumer,
>> and then
>> the consumer goes away, AMQ 4.x broker consumes memory. Is there
>> any way
>> to configure how much it will attempt to keep in memory for
>> persistent
>> messages?? Seems to me that's the point of having the persistence
>> mechanism (i.e. derby or kaha or Oracle) - capacity at that level
>> is not
>> an issue. I can't have the Broker attempting to keep all messages
>> ready
>> in memory for that failed consumer - it may run out of memory very
>> quickly.
>>
>
> --
> View this message in context: http://www.nabble.com/Controlling-
> memory-usage-for-persistent-messages-tf2382626.html#a6735220
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Re: Controlling memory usage for persistent messages
Posted by terrytriple <te...@edinburgh.net.uk>.
Afraid I can't help with your question, but I'm looking for an answer to the
same question !
We are thinking of moving from a JBossMQ solution to ActiveMQ -- but having
the broker block/throw exceptions because it's out of memory due to it
holding all the messages in memory is a real problem for us. With our
existing solution we sometimes have hundreds of thousands of messages
waiting around.
anyway - looking forward to any reponse to this issue !
yaussy wrote:
>
> When sending persistent messages (durable topics) to a consumer, and then
> the consumer goes away, AMQ 4.x broker consumes memory. Is there any way
> to configure how much it will attempt to keep in memory for persistent
> messages?? Seems to me that's the point of having the persistence
> mechanism (i.e. derby or kaha or Oracle) - capacity at that level is not
> an issue. I can't have the Broker attempting to keep all messages ready
> in memory for that failed consumer - it may run out of memory very
> quickly.
>
--
View this message in context: http://www.nabble.com/Controlling-memory-usage-for-persistent-messages-tf2382626.html#a6735220
Sent from the ActiveMQ - User mailing list archive at Nabble.com.