You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2025/11/03 07:07:00 UTC

[jira] [Updated] (AMQ-9447) ActiveMQ Jolokia health service returns "good" even when persistence or transports are failing

     [ https://issues.apache.org/jira/browse/AMQ-9447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated AMQ-9447:
--------------------------------------
    Fix Version/s: 6.2.1
                       (was: 6.2.0)

> 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.1
>
>          Time Spent: 2.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)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact