[ https://issues.apache.org/jira/browse/AMQ-9447?focusedWorklogId=912393&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-912393 ]
ASF GitHub Bot logged work on AMQ-9447: --------------------------------------- Author: ASF GitHub Bot Created on: 31/Mar/24 18:22 Start Date: 31/Mar/24 18:22 Worklog Time Spent: 10m Work Description: AM-19 commented on PR #1192: URL: https://github.com/apache/activemq/pull/1192#issuecomment-2028855845 Hello @jbonofre Have Re-opened as #1194 Sorry for the inconvenience. Thanks Anubhav Issue Time Tracking ------------------- Worklog Id: (was: 912393) Time Spent: 50m (was: 40m) > 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: 50m > 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)