[ https://issues.apache.org/jira/browse/QPID-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-6678: ----------------------------- Fix Version/s: qpid-java-6.0 > Deleting an exchange that is referenced as alternate apparently succeeds but > marks the exchange as DELETED > ---------------------------------------------------------------------------------------------------------- > > Key: QPID-6678 > URL: https://issues.apache.org/jira/browse/QPID-6678 > Project: Qpid > Issue Type: Bug > Components: Java Broker > Affects Versions: 0.32, qpid-java-6.0 > Reporter: Keith Wall > Assignee: Alex Rudyy > Fix For: qpid-java-6.0 > > Attachments: > 0001-QPID-6678-Deletion-of-exchanges-set-as-alternate-exc.patch > > > If I create two exchanges using the Web Management, exch1 and exch2, and make > *exch2* the alternate exchange of *exch1*, I expect to be prevented from > deleting exch2 as exch1 refers to it. This does not happen. If I delete > *exch2* using Management, the operation apparently succeeds, but the object > is recorded in the store as having desiredState DELETED. If I then go on to > restart the Broker, the exchange is removed from the store. If I restart the > Broker a second time, the VH goes into ERROR state as exch1 has a > non-existent alternate exchange. -- 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