onfirm that it is just the stats that
> are wrong in this case, and that all expected messages are getting
> delivered as expected.
>
> On 9 September 2010 14:28, Colleen Velo wrote:
> > Gary,
> >
> > That doesn't seem to be the case here - namely, the
s
onto the
queue, so the # of "Pending Messages" wasn't changing).
On Thu, Sep 9, 2010 at 5:44 AM, Gary Tully wrote:
> Is it by any chance the inflight count in jconsole that is negative?
> There is a good explanation for that,
> http://blog.garytully.com/2010/01/activ
consumers
Thoughts?
Thanks,
--
Colleen Velo
*email: cmv...@gmail.com*
, start up multiple Producers, both of which are throwing
80,000+ messages
to the two brokers (which are configured as a network of brokers ) and have
two consumers running on
separate servers pulling items off of the application queue(s).
On Wed, Sep 8, 2010 at 3:39 PM, Colleen Velo wrote:
> Gary
consumers
running on
separate servers pulling items off of the application queue.
On Wed, Sep 1, 2010 at 8:52 AM, Gary Tully wrote:
> does jconsole show the same negative number? Do you have a test case?
>
> On 1 September 2010 13:52, Colleen Velo wrote:
> > After only running my 3 A
Gary,
Forgot to add that I do see the same thing in JConsole, that is the negative
counts.
On Fri, Sep 3, 2010 at 1:37 PM, Colleen Velo wrote:
> Gary,
>
> Thanks for the clarification - still working on a JUnit test.
> Currently right now the steps that I use to reproduce it is
>
e know if you have any more questions and I'll pass along the JUnit
test as soon
as I can get one to fail consistently.
Thanks,
--
Colleen Velo
email: cmv...@gmail.com
On Thu, Sep 2, 2010 at 2:25 AM, Gary Tully wrote:
> Some series of steps that can reproduce or in the ideal case a jun
ic that is
running
currently in our Product environment with ActiveMQ server version 5.2.0.
What would you need exactly for a "test" case?
Thanks,
--
Colleen Velo
*email: cmv...@gmail.com*
On Wed, Sep 1, 2010 at 8:52 AM, Gary Tully wrote:
> does jconsole show the same negative num
87
It was recommended that I upgrade to ActiveMQ 5.4.0, which I did, however, I
am still
seeing this issue.
Current Environment:
• CentOS release 5.2 (both consumers and brokers)
• 3 ActiveMQ brokers
• 7 consumers (across different queues)
Thanks,
--
Colleen Velo
email: cmv...@gmail.com
