Hi Steve- These settings are lower than the default and generally lead to degraded consumer performance. Any reason you lowered the maxPageSize from 200 to 10? What only allow 1 message prefetch— the default is 1,000?
Thanks, Matt Pavlovich > On Jan 23, 2024, at 9:58 AM, Steve Hill <sh...@futurelogix.co.uk> wrote: > > Hi: > > We have successfully been using ActiveMQ Classic for many years. Currently we > are running ActiveMQ 5.15.4 and it successfully processes millions of > messages without issue. Our setup is fairly simple, we have it operating in > master/slave fashion utilizing shared storage in the event ActiveMQ fails > from one node to another. > > Several years ago we attempted to upgrade to 5.16.x but ended up having to > remove it from production as we were seeing performance issues. We have now > attempted to upgrade to 5.18.3 and again are experiencing delays; fortunately > this time we caught it in our test environment! > > This is consistent across applications that are consuming from the queue's, > we are seeing the initial time to retrieve the message from the queue goes > from near instantaneous on 5.15.4 to 1-3 second pause after upgrading to > 5.18.3. We make use of pooled connections to ActiveMQ, depending on the > queue there could be between 5 and 80 consumers. The configuration is > vanilla and the following policy is the largest change. > > > <policyEntry queue=">" enableAudit="false" producerFlowControl="false" > queuePrefetch="1" maxPageSize="10" lazyDispatch="true" > expireMessagesPeriod="600000"> > </policyEntry> > > Does anyone have any ideas about how we can diagnose the issue further; we > would really like to become current on the version of ActiveMQ we are running. > > Thanks! > Steve. >
