[
https://issues.apache.org/jira/browse/ARTEMIS-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422975#comment-17422975
]
Justin Bertram commented on ARTEMIS-3505:
-----------------------------------------
Thanks for the clarification. I read through ARTEMIS-3355 to re-familiarize
myself with that issue. At this point there is no clear evidence that this
issue is actually the same as ARTEMIS-3355 despite your assertion that they
are.
In ARTEMIS-3355 the thread dump contained a {{BLOCKED}} thread and another
{{WAITING}} thread which clearly demonstrated the problem. The thread dump for
this issue has no such threads. In fact, there's no clear evidence at all
indicating what the underlying problem might be. Therefore, I stand by my
statement that ARTEMIS-3355 is fixed.
In short, the critical analyzer might halt the broker for any number of
reasons. There's no evidence to suggest the reason it halted the broker here is
the same as on ARTEMIS-3355.
Lastly, I modified your previous comment as cutting & pasting such a long and
unrelated comment from ARTEMIS-3355 was unnecessary and confusing. Anybody who
wants the details of ARTEMIS-3355 can simply go there and read them.
> 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: samplebroker.xml, 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)
