Thanks for taking the time to post your findings!
On Thu, Aug 29, 2013 at 6:05 PM, stormtrooper wrote:
> Hello,
>
> Well, we've figured this out so I'll record it here for posterity.
>
> Our master/slave setup was incorrectly configured.
>
> Originally our architecture was going to have two cl
Hello,
Well, we've figured this out so I'll record it here for posterity.
Our master/slave setup was incorrectly configured.
Originally our architecture was going to have two clusters that talked to
each other. In our phased development approach we scaled back to work with
just one initially. H
That's quite odd.
Can you reproduce this on KahaDB? ie, kahadb is supported for shared master
slave (http://activemq.apache.org/shared-file-system-master-slave.html) and
it might be easier to debug (without the dependency on the DB) if you can
recreate with KahaDB...
What do the broker stats say a
bump. Could someone take a peek at this again and see if they have any
ideas?
(we tried prefetch size = 0 on the client connection URL, and that didn't
change anything)
Thanks!
Les
On Mon, Jul 22, 2013 at 7:10 PM, stormtrooper wrote:
> Hello all,
>
> Using ActiveMQ 5.8.0 we are seeing a mess
