[
https://issues.apache.org/jira/browse/ARTEMIS-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447990#comment-17447990
]
Francesco Nigro commented on ARTEMIS-3587:
------------------------------------------
I see that logs and JIRA description won't agree on which path has been expired
ie
expired on path 4 (desc) vs expired on path 2 (log)
They can caused and seems 2 separate issues: the HW running the broker is the
same? Have you tried with a recentish version?
Consider that having the stack trace to agree on the critical analyzer path is
key to spot what's the issue here, or we can just guess...
Indeed my first guess looking at the log stack trace is that there must be some
heavy filter logic in place; there is something re it that has changed recently?
> 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
> Attachments: log_with_stacktrace.log
>
>
> 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)
