Off the top of my head, I can think of the following:
* all messages are published with the same group ID
* one consumer has a selector that doesn't match any messages
* one consumer is on a different broker in a network of brokers and you've
set decreaseNetworkConsumerPriority to true
I'd bet I c
e ack's are out of order from
receive's.
That's quite likely to happen as different messages take different amounts
of time to process.
-Original Message-
From: Christian Posta [mailto:christian.po...@gmail.com]
Sent: Friday, April 26, 2013 5:54 PM
To: users@activemq.apac
I duplicated this behavior on RedHat Linux with 5.6.0 and sleep(600);
To recap at this point:
Sleep(500) works fine, Sleep(600) gets an exception, Sleep(1000) misses the
1st message.
So it's not platform dependent. Given the error I see I don't think it's
necessarily related to my original proble
q.apache.org
Subject: Re: Dispatched Queue Size
Let us know what happens if you run on a LAN. If you can post your
code/configs, or better yet, create a unit test that shows this, it'll be
much easier to tell you what's going on.
On Fri, Apr 26, 2013 at 8:28 AM, mdblack98 wrote:
>
uot;);
}
}
}
-Original Message-
From: Christian Posta [mailto:christian.po...@gmail.com]
Sent: Friday, April 26, 2013 5:54 PM
To: users@activemq.apache.org
Subject: Re: Dispatched Queue Size
Let us know what happens if you run on a LAN. If you can post your
code/configs, or better yet, create a unit test that shows this, it'll be
much easier to tell you what's going on.
Let us know what happens if you run on a LAN. If you can post your
code/configs, or better yet, create a unit test that shows this, it'll be
much easier to tell you what's going on.
On Fri, Apr 26, 2013 at 8:28 AM, mdblack98 wrote:
> Do I need to post my client code to get an answer to this?
>
Do I need to post my client code to get an answer to this?
I can reproduce that at any time quite easily. It happens continuously
while the client is running. A little less than 1% of the total number of
messages end up not showing Dequeued but they are actually being processed
and ack'd.
The "Di
