[ 
https://issues.apache.org/jira/browse/DISPATCH-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168106#comment-16168106
 ] 

ASF GitHub Bot commented on DISPATCH-821:
-----------------------------------------

GitHub user kgiusti opened a pull request:

    https://github.com/apache/qpid-dispatch/pull/197

    DISPATCH-821: actually delete the configured address

    Well..... that was stupid.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kgiusti/dispatch DISPATCH-821

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-dispatch/pull/197.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #197
    
----
commit 355942a8a0a4aa4c221d90272c1960542fe3b37d
Author: Kenneth Giusti <[email protected]>
Date:   2017-09-15T16:00:20Z

    DISPATCH-821: actually delete the configured address

----


> recreating an address immediately after deleting it, results in error
> ---------------------------------------------------------------------
>
>                 Key: DISPATCH-821
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-821
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Gordon Sim
>            Assignee: Ken Giusti
>             Fix For: 1.0.0
>
>         Attachments: dispatch_821.py
>
>
> If an address is deleted, then *after* the router confirms the deletion, it 
> is immediately recreated, the router responds with an error to the create - 
> {"statusDescription"="Address prefix conflicts with an existing entity", 
> "statusCode"=400}. Subsequent queries do not show the address but it can't be 
> created either.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to