Can you past the full log to help troubleshooting which path is now interested by it?
Il lun 22 nov 2021, 12:35 Sebastian T (Jira) <j...@apache.org> ha scritto: > Sebastian T created ARTEMIS-3587: > ------------------------------------ > > Summary: After upgrade: AMQ224107: The Critical Analyzer > detected slow paths on the broker. > Key: ARTEMIS-3587 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3587 > Project: ActiveMQ Artemis > Issue Type: Bug > Affects Versions: 2.19.0 > Reporter: Sebastian T > > > After upgrading from Artemis 2.16.0 to 2.19.0 we now receive the following > message a view times a day: > > 2021-11-05 05:32:53.641 WARN 3850 --- [eduled-threads)] > o.a.a.a.u.c.CriticalMeasure : Component > org.apache.activemq.artemis.core.server.impl.QueueImpl is expired on path 4 > 2021-11-05 05:32:53.642 INFO 3850 --- [eduled-threads)] o.a.a.a.c.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. > > This message is also logged via > ActiveMQServerCriticalPlugin#criticalFailure however the javadoc says: > "This will be called before the broker is stopped." The broker however is > not stopped. So I think the javadoc and the behaviour of the callback are > not in line anymore too. > > > > -- > This message was sent by Atlassian Jira > (v8.20.1#820001) >
