[
https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy resolved QPID-8086.
------------------------------
Resolution: Fixed
The tool implementation looks OK to me, though, it is really a
{{ConfigurationRecordPurger}} rather than {{OrphanConfigurationRecordPurger}},
as it can delete any configuration entry and it does not check whether it is
orphan or not. Potentially, it can be further improved to evaluate the orphan
records based on information stored in the store rather than from command line
arguments {{-targetUuid}}. As it is unlikely, that anyone would ever ran into
the defect, I am ok to leave the implementation as it is.
> [Broker-J] Create tool to permit recovery from QPID-8066
> --------------------------------------------------------
>
> Key: QPID-8086
> URL: https://issues.apache.org/jira/browse/QPID-8086
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Major
> Fix For: qpid-java-broker-7.0.1, qpid-java-6.1.6
>
>
> Defect QPID-8066 has the potential to leave the Broker in a state where it
> cannot be restarted. The recovery phase, on encountering the orphan records,
> throws an exception and this puts the virtualhost into an {{ERROR}} state.
> There is no facility in Broker-J to recover from this short of recreation of
> the virtualhost.
> If the configuration store is backed by JDBC, then a workaround is to connect
> to the database and remove the offending rows. Unfortunately if the
> virtualhost is backed by BDB (for configuration) or BDB HA, the user has no
> convenient way to recover the situation. BDB JE has no command line
> interface so a Java program would have to be written with knowledge of the
> store's structure. The HA case is further complicated by the fact that
> sufficient nodes would have to be available to provide quorum within the
> group.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
