[
https://issues.apache.org/jira/browse/AMQ-9447?focusedWorklogId=914095&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-914095
]
ASF GitHub Bot logged work on AMQ-9447:
---------------------------------------
Author: ASF GitHub Bot
Created on: 11/Apr/24 07:12
Start Date: 11/Apr/24 07:12
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #1194:
URL: https://github.com/apache/activemq/pull/1194#issuecomment-2049061906
This first step checking the transports looks good to me. I would also check
the storage service.
Issue Time Tracking
-------------------
Worklog Id: (was: 914095)
Time Spent: 1h (was: 50m)
> ActiveMQ Jolokia health service returns "good" even when persistence or
> transports are failing
> ----------------------------------------------------------------------------------------------
>
> Key: AMQ-9447
> URL: https://issues.apache.org/jira/browse/AMQ-9447
> Project: ActiveMQ Classic
> Issue Type: Improvement
> Components: Broker, JMX
> Affects Versions: 5.18.3
> Reporter: Ephemeris Lappis
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 6.2.0, 5.18.5
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The Jolokia health service only considers the BrokerService status, it
> doesn't check all layers (like persistent store or transports).
> The CurrentStatus should not be "Good" if some underlying service is failing.
> For example, with a JDBC persistence adapter, if the DB is not reachable, the
> broker should not be considered as OK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
