qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6678) Deleting an exchange that is referenced as alternate apparently succeeds but marks the exchange as DELETED
Date Tue, 15 Sep 2015 16:40:45 GMT

    [ https://issues.apache.org/jira/browse/QPID-6678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745701#comment-14745701

ASF subversion and git services commented on QPID-6678:

Commit 1703250 from orudyy@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1703250 ]

QPID-6678: Address review comments from Keith Wall

           Remove a number of redundant methods for exchange deletion and replace invocation
of deleted methods with Exchange#delete
           ExchangeExistsException, QueueExistsException, ExchangeIsAlternateException, RequiredExchangeException
extends IntegrityViolationException to simplify exception handling in management layers
           Set attain state future even when state transition method invocation results in

> 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
>         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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message