[ 
https://issues.apache.org/jira/browse/QPID-7972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374206#comment-16374206
 ] 

ASF GitHub Bot commented on QPID-7972:
--------------------------------------

Github user overmeulen commented on the issue:

    https://github.com/apache/qpid-broker-j/pull/4
  
    Hello,
    
    Yes it would answer my use case. Actually I considered this option when 
doing the dev but I wasn't very fond of the Broker checking the whole tree of 
children nodes... I found it better to keep each node aware of just its direct 
children and it looked more correct to actually put the VirtualHostNode in 
ERRORed state too.
    
    Olivier


> Virtual Host Node should be in error state if the underlying Virtual Host is 
> in error state
> -------------------------------------------------------------------------------------------
>
>                 Key: QPID-7972
>                 URL: https://issues.apache.org/jira/browse/QPID-7972
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Broker-J
>    Affects Versions: qpid-java-6.1.4
>            Reporter: Adel Boutros
>            Priority: Major
>
> All details can be found here: 
> http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-6-1-4-Broker-is-ready-even-if-an-error-is-occuring-on-startup-and-failStartupWithEre-tp7668029.html



--
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

Reply via email to