You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2021/12/15 13:57:00 UTC
[jira] [Closed] (ARTEMIS-3587) After upgrade: AMQ224107: The Critical Analyzer detected slow paths on the broker.
[ https://issues.apache.org/jira/browse/ARTEMIS-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clebert Suconic closed ARTEMIS-3587.
------------------------------------
Fix Version/s: 2.20.0
Resolution: Fixed
> 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
> Components: Broker
> Affects Versions: 2.19.0
> Reporter: Sebastian T
> Priority: Major
> Labels: performance
> Fix For: 2.20.0
>
> Attachments: log_with_stacktrace.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After upgrading from Artemis 2.16.0 to 2.19.0 we now receive the following message a few 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)