Alex Rudyy created QPID-6126:
--------------------------------

             Summary: [Java Broker] Improve CO validation on creation and 
transit CO into ERRORED state on exceptions whilst recovering
                 Key: QPID-6126
                 URL: https://issues.apache.org/jira/browse/QPID-6126
             Project: Qpid
          Issue Type: Improvement
          Components: Java Broker
         Environment: Java Broker cannot start when exceptions occus on 
recovery of configured objects. Management mode is required to use in order to 
remediate the configuration issue. However, in some cases configured objects 
cannot even be started in management mode. Additionally, there are number 
issues with attribute validation on creation of COs, like CO is created but 
cannot be stored in configuration store. Sometimes, such CO cannot even be 
deleted properly from the broker model and restart is required to remove such 
COs.

This JIRA aims to sthengthen CO validation and improve Broker behaviour on 
recovery/creation of CO with misconfigured attributes.

The following improvements will be added as part of this JIRA:
# a special method to implement validation on creation will be added into 
AbstractConfiguredObject and COs inherited from AbstractConfiguredObject to 
perform additional attribute validation on creation. Validation exceptions 
thrown from the validation methods on CO creation should delete CO and release 
all its resources.
# when runtime exceptions occur on CO recovery such CO should transit into 
ERRORED state and Broker should continue with the startup of not-impacted COs.
#user should be able to remediate the configuration issue in ERRORED CO using 
management interfaces and re-start the CO

            Reporter: Alex Rudyy
            Assignee: Alex Rudyy
             Fix For: 0.31






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to