Hi Naaman,
persistent messages sent to durable subscribers are always stored to
a persistent store. However, references to the stored messages are
held in memory - so it can be possible if a large number of messages
are sent to a non-active durable subscriber for the broker to stop
processing until more free memory is available for the message
references
There will be a solution for this in the next release
cheers,
Rob
On 3 Sep 2006, at 09:00, nlif wrote:
Hi,
I am using a topic to publish to multiple clients. Since
communication with
some of the clients may be intermittent, I want to use a durable
topic, so
that messages will be kept for clients not connected at the moment of
publishing. However, here is my concern: some of my clients may be
down for
a very long time (hours or even days). I assume topic durability is
implemented by storing messages in broker memory, and therefore, I am
concerned that as more and more messages accumulate in memory the
broker
will be brought down, or will simply refuse to accept new messages
until old
messages are delivered. I would like to know if there is any
solution to
this issue, such as dumping messages to database after a while, so
they are
available when the client finally shows up, but do not take up
memory in the
meantime.
Thanks,
Naaman
--
View this message in context: http://www.nabble.com/Durable-topics-
question-tf2209716.html#a6120042
Sent from the ActiveMQ - User forum at Nabble.com.
