[
https://issues.apache.org/jira/browse/QPID-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy resolved QPID-6194.
------------------------------
Resolution: Fixed
Fix Version/s: 0.31
The changes look good to me. The only thing I would change in addition to the
already made changes, I would delete dead methods like addPlugin, gertPlugins,
etc and inline such methods like addAuthenticationProvider, addPort, etc. I
suppose we can do it on following BrokerAdaptor modifications
> Allow Qpid broker to be configured to fail to start if it has a child object
> in ERRORED state
> ---------------------------------------------------------------------------------------------
>
> Key: QPID-6194
> URL: https://issues.apache.org/jira/browse/QPID-6194
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Andrew MacBean
> Assignee: Andrew MacBean
> Fix For: 0.31
>
>
> In previous version sof the Java broker startup would fail if any of the
> brokers children were in an errored state.
> In order to allow a user to keep that behaviour in the latest version a
> broker context variable should be added to allow the broker to behave like it
> used to.
> The UI might also benefit from having a visual indicator at broker level
> highlighting ERRORED child objects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
