[ https://issues.apache.org/jira/browse/AMQ-9447?focusedWorklogId=912391&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-912391 ]
ASF GitHub Bot logged work on AMQ-9447: --------------------------------------- Author: ASF GitHub Bot Created on: 31/Mar/24 17:38 Start Date: 31/Mar/24 17:38 Worklog Time Spent: 10m Work Description: AM-19 closed pull request #1192: [AMQ-9447] Added Logic to check underlying transport connector limits URL: https://github.com/apache/activemq/pull/1192 Issue Time Tracking ------------------- Worklog Id: (was: 912391) Time Spent: 0.5h (was: 20m) > 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: 0.5h > 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)