Yah, you can specify different ACK modes and ack explicitly if you like.
Otherwise they are just auto-acked.
Check out Raul's great blog post on JMS Ack modes:
http://blog.raulkr.net/2012/08/consumer-acknowledgements-in-activemq.html
On Thu, Jan 3, 2013 at 3:43 PM, Mohit Anchlia wrote:
> Just o
Just one more question, is there a way to force acknowledgment of a message
or send it to DLQ? I am wondering what safeguards we can put in place in
active mq so that if and when this occurs it doesn't impact all other
clients.
On Thu, Jan 3, 2013 at 7:57 AM, Mohit Anchlia wrote:
> Yes it's reall
Yes it's really helpful. Thanks again
On Thu, Jan 3, 2013 at 5:33 AM, Christian Posta
wrote:
> Good call Claus. I've updated the wiki page here:
>
> http://activemq.apache.org/how-do-i-find-the-size-of-a-queue.html
>
> Should be a couple hours to propagate through.
>
> Thanks!
>
>
> On Thu, Jan 3
Good call Claus. I've updated the wiki page here:
http://activemq.apache.org/how-do-i-find-the-size-of-a-queue.html
Should be a couple hours to propagate through.
Thanks!
On Thu, Jan 3, 2013 at 1:05 AM, Claus Ibsen wrote:
> On Wed, Jan 2, 2013 at 9:33 PM, Christian Posta
> wrote:
> > Enqueu
On Wed, Jan 2, 2013 at 9:33 PM, Christian Posta
wrote:
> Enqueue count = number of messages sent to the queue
> Dequeue count = number of messages ack'd by the consumer
> Inflight count = number of messages sent to consumer's session (and are not
> ack'd by consumer)
> Dispatch count = messages se
So persistent=true is a broker setting. The setting in question for your
scenario is that for the client (producer) of the message.
See here:
http://activemq.apache.org/what-is-the-difference-between-persistent-and-non-persistent-delivery.html
On Wed, Jan 2, 2013 at 2:02 PM, Mohit Anchlia wrote
Thanks for the info. I'll look at those parameter.
It does look like that I am using persistence based on below
"persistent=true" parameter. So can I safely assume that only one producer
gets blocked?
http://activemq.apache.org/schema/core";
brokerName="static-broker1" persistent="true"
dataDirec
Yah, it's probably best to figure out how things are being sent right now.
If messages are sent async and without a producer window then you'll hit
the type of flow control that you did.
Messages are sent async by default if using non-persistent messages or
during a transaction. The only time any
Thanks! Sounds like there might be another way we can configure the flow
control that blocks only one producer? Do you have any recommendation on
what changes I should make to the config?
On Wed, Jan 2, 2013 at 12:33 PM, Christian Posta
wrote:
> Enqueue count = number of messages sent to the queu
Enqueue count = number of messages sent to the queue
Dequeue count = number of messages ack'd by the consumer
Inflight count = number of messages sent to consumer's session (and are not
ack'd by consumer)
Dispatch count = messages sent to the consumer (dequeue + inflight)
I asked about the async s
Thanks again! Is the dispatch queue size the one that relates to what's
held in memory?
We are using mule and the endpoint has no transactions configured. What did
you mean by forcing async?
On Wed, Jan 2, 2013 at 11:06 AM, Christian Posta
wrote:
> Correct. The memoryUsage is increased when mess
Correct. The memoryUsage is increased when messages are held in memory.
This happens when messages are paged in from the store. They are then
dispatched to consumers and held until the consumer acks.
In your case looks like a particular destination (eventsEndpoint) is
filling up somehow. Can you l
So if I understand correctly I shouldn't be seeing this behaviour unless
something is being held in memory. We ack immediately so I am kind of
wondering what might be going on here. Is there a way to find out what
might be happening here?
On Wed, Jan 2, 2013 at 10:03 AM, Christian Posta
wrote:
>
What info can you provide about how clients are consuming from the queues?
Any chance there are a bunch of messages "inflight" which haven't been
ack'd by the consumer?
On Wed, Jan 2, 2013 at 10:20 AM, Mohit Anchlia wrote:
> I see these messages being logged. Queues are setup to use persistent
>
14 matches
Mail list logo
