qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-8086) [Broker-J] Add ability to the Broker to permit recovery from QPID-8066
Date Wed, 24 Jan 2018 15:37:01 GMT

     [ https://issues.apache.org/jira/browse/QPID-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Wall updated QPID-8086:
-----------------------------
    Description: 
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 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.

  was:
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 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.

 

 


> [Broker-J] Add ability to the Broker 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
>            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
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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message