Maybe the issue is that effectively some component is blocked due to lack of CPU or some external slow component: can you share the full stack and some statistics about the machine and hw component?
Il giorno gio 16 set 2021 alle ore 15:53 foo bar <statuario...@gmail.com> ha scritto: > 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 >
