[
https://issues.apache.org/jira/browse/ARTEMIS-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423010#comment-17423010
]
Ekta commented on ARTEMIS-3505:
-------------------------------
Thanks for clarifying.
So far we are seeing this critical analyzer detected slow paths quiet
frequently unless like before. I also see that it is happening on various
different components and different paths every time. Below are few examples.
2021-09-29 17:23:56,752 ERROR [org.apache.activemq.artemis.core.server]
AMQ224079: The process for the virtual machine will be killed, as component
QueueImpl[name=xxx.xxxx.unicast, postOffice=PostOfficeImpl
[server=ActiveMQServerImpl::name=activemq-prod-master2a], temp=false]@546c87a1
is not responsive
2021-09-29 17:23:56,751 WARN
[org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
org.apache.activemq.artemis.core.server.impl.QueueImpl is expired on path 2
2021-09-29 15:27:47,796 ERROR [org.apache.activemq.artemis.core.server]
AMQ224079: The process for the virtual machine will be killed, as component
org.apache.activemq.artemis.core.io.buffer.TimedBuffer@746892b7 is not
responsive
2021-09-29 15:27:47,795 WARN
[org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
org.apache.activemq.artemis.core.io.buffer.TimedBuffer is expired on path 3
2021-09-20 15:04:08,502 ERROR [org.apache.activemq.artemis.core.server]
AMQ224079: The process for the virtual machine will be killed, as component
org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager@7aef86b7
is not responsive
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
2021-09-20 15:04:08,501 WARN
[org.apache.activemq.artemis.utils.critical.CriticalMeasure] Component
org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager
is expired on path 0
After reviewing our case, would you still recommend us to try LOG in lower
environment and wait & see as we can't reproduce this. In case the server is
running in the background with some deadlocks, what are the chances it would
clear own its own and if so, the time estimate? Assuming the server won't be
able to function until it clears the deadlock in the background, as the server
will still be up but won't be processing any live traffic.
Appreciate your help on this.
Thanks again.
> 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)
