I think perhaps you've misunderstood the issue reported via ARTEMIS-3271 [1]. The issue was that the critical analyzer [2] would sometimes report false positives. The fix eliminated the false positives, but it didn't eliminate *all* reports. You may be hitting an actual issue. In order to investigate further you need to provide the thread dump logged by the critical analyzer.
For what it's worth, you can configure the critical analyzer to just log the issue and not shutdown the broker. The documentation [2] has the configuration details. Justin [1] https://issues.apache.org/jira/browse/ARTEMIS-3271 [2] https://activemq.apache.org/components/artemis/documentation/latest/critical-analysis.html On Thu, Sep 16, 2021 at 8:54 AM foo bar <statuario...@gmail.com> wrote: > Hello, > > We are using ArtemisMQ version 2.15. We are attempting to upgrade to 2.18. > On 2.18, we generate some load with a couple of threads. We are getting the > exact same error noted here: > > https://www.mail-archive.com/issues@activemq.apache.org/msg58016.html > > ``` > [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component > org.apache.activemq.artemis.core.server.impl.QueueImpl is expired on path 0 > 2021-05-15 10:00:49,258 > INFO [org.apache.activemq.artemis.core.server] > AMQ224107: The Critical Analyzer detected slow paths on the broker. It is > recommended that you enable trace logs on > org.apache.activemq.artemis.utils.critical while you troubleshoot this > issue. > You should disable the trace logs when you have finished troubleshooting. > 2021-05-15 10:00:49,258 ERROR [org.apache.activemq.artemis.core.server] > AMQ224079: The process for the virtual machine will be killed, as component > QueueImpl[name=q_7, postOffice=PostOfficeImpl > > [server=ActiveMQServerImpl::serverUUID=64e3f254-b585-11eb-8f02-000f532921b8], > > temp=false]@9a33f70 is not responsive > 2021-05-15 10:00:50,429 WARN [org.apache.activemq.artemis.core.server] > AMQ222199: Thread dump: > ``` > > I do see a ticket here noting that the issue has been resolved in 2.18, > although we just encountered it. > > > https://issues.apache.org/jira/browse/ARTEMIS-3271?focusedWorklogId=597221&page=com.atlassian.jira.plugin.system.issuetabpanels%3Aworklog-tabpanel#worklog-597221 > > Once this happens the broker is down and needs to be restarted. Is there a > workaround for this? > > Thanks >
