[
https://issues.apache.org/jira/browse/ARTEMIS-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422634#comment-17422634
]
Gary Tully commented on ARTEMIS-3505:
-------------------------------------
can you post your broker.xml?
What is unusual is that the thread that fails the check (being in the critical
section for too long) is not in the thread dump.
That may be that the limit is too low for this system, and if it was a little
longer, the delay would go unnoticed.
In addition, the delay is being treated a fatal and terminating the broker, you
can configure the behaviour to just log the thread dump and continue. It does
not need to terminate.
the other point, as suggested in the thread dump: 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.
Could you do that?
> Activemq Broker Keeps Crashing
> ------------------------------
>
> Key: ARTEMIS-3505
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3505
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.18.0
> Environment: DEV/UAT/PROD
> Reporter: Ekta
> Priority: Critical
> Attachments: threadDump.txt
>
>
> Hello All,
>
> We have noticed the same problem which we reported earlier with 2.17 and
> were told that it would be fixed in 2.18 version. We have recently moved all
> our environments to 2.18 version and can see the problem still exists across
> all of our env's.
>
> We have below architecture in respect to activemq master/slave setup.
> {noformat}
> producer/consumer --> Apache QPID (1.14) --> Artemis 2.18 (master/slave)
> {noformat}
> Basically, we see our master and slave brokers going down abruptly with below
> log. I have also attached the thread dump for analysis to see if anyone can
> spot anything, for sure we can see it is to do with some concurrent
> deadlocks. Please go through the attached logs and suggest any feedback, if
> any.
> The log that is causing the issue is highlighted below, as soon as the broker
> prints this, it prints The Critical Analyzer detected slow paths on the
> broker. *and therefore*, AMQ224079: The process for the virtual machine will
> be killed.
> 2021-09-29 10:37:43,327 WARN
> [org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
> org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 4
> It has been happening quite frequently now and we need to come to bottom of
> this.
>
> Appreciate everyone's effort on this. [^threadDump.txt]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
