[
https://issues.apache.org/jira/browse/QPID-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377134#comment-16377134
]
ASF subversion and git services commented on QPID-8110:
-------------------------------------------------------
Commit 3bbf01a0b44192fd3e04264230ebc14e4abe3c7a in qpid-broker-j's branch
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=3bbf01a ]
QPID-8110: [Broker-J] Add ability to check ERRORED state of entire configured
object hierarchy
This closes #4
https://github.com/apache/qpid-broker-j/pull/4
(cherry picked from commit b720d7d1e81324441b8fbc2850ef19ca0fdf9bda)
> [Broker-J] Add ability to check ERRORED state of entire configured object
> hierarchy on broker startup
> -----------------------------------------------------------------------------------------------------
>
> 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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
