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

ASF GitHub Bot commented on QPID-7875:
--------------------------------------

GitHub user chrisrichardson77 opened a pull request:

    https://github.com/apache/qpid-cpp/pull/6

    QPID-7875 qpid-route fetches links multiple times when deleting routes

    See https://issues.apache.org/jira/browse/QPID-7875

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

    $ git pull https://github.com/fourceu/qpid-cpp qpid-route-use-existing-link

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

    https://github.com/apache/qpid-cpp/pull/6.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 #6
    
----
commit 88f9ed29607c07d7d82c3a2a8b34e6d69ed3324e
Author: Chris Richardson <[email protected]>
Date:   2017-08-01T14:12:59Z

    QPID-7875 qpid-route fetches links multiple times when deleting routes

----


> qpid-route fetches links multiple times when deleting routes
> ------------------------------------------------------------
>
>                 Key: QPID-7875
>                 URL: https://issues.apache.org/jira/browse/QPID-7875
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: qpid-cpp-1.36.0
>            Reporter: Chris Richardson
>
> When deleting routes/queue routes, qpid-route first retrieves the 
> inter-broker link on which the route is to be deleted, then (having deleted 
> the bridge and only if configured to delete the link) gets the same link 
> again in order to close it. This results in an extra RPC call which 
> unnecessarily reads all links from the broker a second time.
> PR:



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