[
https://issues.apache.org/jira/browse/ARTEMIS-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422922#comment-17422922
]
Justin Bertram commented on ARTEMIS-3504:
-----------------------------------------
This message is being logged by the [critical
analyzer|https://activemq.apache.org/components/artemis/documentation/latest/critical-analysis.html].
It should be accompanied by a couple other log messages and a thread dump. Are
you certain you don't see any additional information like this in your log?
If you don't want the critical analyzer to stop the broker when it detects a
serious problem then you can change the configuration (e.g.
{{<critical-analyzer-policy>LOG</critical-analyzer-policy>}}). However, I
recommend you investigate _why_ the critical analyzer halted the broker in the
first place as you may be dealing with a more serious configuration or
environmental issue.
If you have additional questions or comments please start a thread on the
[ActiveMQ users mailing list|http://activemq.apache.org/contact].
> AMQ224080: The server process will now be stopped, as component
> JournalStorageManage is not responsive
> ------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3504
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3504
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.18.0
> Reporter: André Hurschler
> Priority: Major
>
> We get this error again at different times in a productive system without
> stack-traces or additional information:
> {noformat}
> AMQ224080: The server process will now be stopped, as component
> org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager@65631036
> is not responsive {noformat}
> We use the ActiveMQ Artemis Native Layer 1.0.2, Red Hat Linux, on a VMWare VM.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
