Hi,
I have 4 consumers - 2 durable and 2 non durable. What I am observing is
that when a durable consumer is down, none of the other consumers get
data! I am using 4.1.1. I am also observing that when a consumer is
down, the memory keeps increasing. The memoryManager element does not
seem to ha
I ran a quick test with the persistent flag set to true and another one
with the flag set to false. In both the cases, I have the consumers
subscribed as durable. I publish messages to the topic while the clients
are up and while they are down. In both the cases, when the clients come
back up, they
task). You
might want to use queues if you want more immediate deletion & freeing
of resources.
Finally using AMQStore in 4.2 should use less disk space than a JDBC
database.
On 4/2/07, Ramesh Bobba <[EMAIL PROTECTED]> wrote:
> Hi James,
>
> I do want to use persistent delivery.
-
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: Monday, April 02, 2007 1:27 AM
To: users@activemq.apache.org
Subject: Re: JDBC Persistance
On 4/1/07, Ramesh Bobba <[EMAIL PROTECTED]> wrote:
> I have three producers producing 80K messages every 2 seconds, I have
> three consumer
I have three producers producing 80K messages every 2 seconds, I have
three consumers subscribed as durable consumers. I am using mysql as
persistence. What I see is that the messages are being written to the
database even when all the subscribers are up. I thought that broker
only writes to the da
