[
https://issues.apache.org/jira/browse/QPID-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111622#comment-16111622
]
Gordon Sim commented on QPID-7874:
----------------------------------
I think it might be good to make it configurable. Though as you say it is not
strictly necessary, checking the link becomes active would be one way of more
immediately highlighting possible issues with the setup. E.g. perhaps the quiet
option might be relevant here, looking through the code it seems that is used
elsewhere to decide whether to raise exceptions or just exit silently. So if
quiet is set, the checks on the link could perhaps be skipped. (I accept that
is a slight change in meaning, but to me it is not too far removed). Wdyt?
> qpid-route performs an unnecessary link check when adding routes
> ----------------------------------------------------------------
>
> Key: QPID-7874
> URL: https://issues.apache.org/jira/browse/QPID-7874
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: qpid-cpp-1.36.0
> Reporter: Chris Richardson
>
> Having connected to the destination broker (for "normal" routes) or source
> broker (for "src-local" routes), the qpid-route utility checks that the
> inter-broker link is active before configuring the new bridge. This check is
> not necessary since the bridge can still be created even if the network link
> is down. When the remote broker becomes accessible, the inter-broker link and
> the bridge will come up as expected.
> PR: https://github.com/apache/qpid-cpp/pull/5
> An alternative to simply removing the check might be to make it a
> configuration option.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
