[ https://issues.apache.org/jira/browse/QPID-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156706#comment-14156706 ]
ASF subversion and git services commented on QPID-6126: ------------------------------------------------------- Commit 1629010 from oru...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1629010 ] QPID-6126: Improve validation and exception messages for BDB HA node > [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 > Reporter: Alex Rudyy > Assignee: Keith Wall > Fix For: 0.31 > > Attachments: > 0001-QPID-6126-Add-ability-to-validate-CO-attributes-on-c.patch, > 0001-QPID-6126-Add-ability-to-validate-CO-attributes-on-c.patch > > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org