You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2018/02/23 15:51:00 UTC
[jira] [Assigned] (QPID-8110) [Broker-J] Add ability to check
ERRORED state on broker startup for entire configured object hierarchy
[ https://issues.apache.org/jira/browse/QPID-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-8110:
--------------------------------
Assignee: Alex Rudyy
> [Broker-J] Add ability to check ERRORED state on broker startup for entire configured object hierarchy
> ------------------------------------------------------------------------------------------------------
>
> Key: QPID-8110
> URL: https://issues.apache.org/jira/browse/QPID-8110
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-broker-7.0.2, qpid-java-broker-7.1.0
>
>
> At the moment, the state of Broker immediate children is checked on Broker startup. If any of immediate childs has an ERRORED state and context variable {{broker.failStartupWithErroredChild}} is set to true, the Broker does not start. This functionality needs to be extended to check the state of entire configured object hierarchy. Thus, if any of configured objects transits into ERRORED state during broker activation, the broker should not be allowed to start.
> This functionality should address pull request [https://github.com/apache/qpid-broker-j/pull/4]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org