[
https://issues.apache.org/jira/browse/DISPATCH-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295524#comment-16295524
]
ASF GitHub Bot commented on DISPATCH-905:
-----------------------------------------
GitHub user ganeshmurthy opened a pull request:
https://github.com/apache/qpid-dispatch/pull/236
DISPATCH-905 - Allow backup port in the failover list to be sent to t…
…he router as PN_INT
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-905
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/236.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 #236
----
commit df1d9a51f67fc9188925427a215d5aa2a47a12f1
Author: Ganesh Murthy <gmur...@redhat.com>
Date: 2017-12-18T19:27:26Z
DISPATCH-905 - Allow backup port in the failover list to be sent to the
router as PN_INT
----
> Dispatch Router not failing over to slave broker when master broker goes away
> -----------------------------------------------------------------------------
>
> Key: DISPATCH-905
> URL: https://issues.apache.org/jira/browse/DISPATCH-905
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 1.0.0
> Reporter: Ganesh Murthy
> Assignee: Ganesh Murthy
> Fix For: 1.1.0
>
> Attachments: broker-master.xml, broker-slave.xml, failover.conf
>
>
> Attached are 3 files
> 1. broker-master.xml (Apache Artemis master broker configuration)
> 2. broker-slave.xml (Apache Artemis slave broker configuration)
> 3. failover.conf (Qpid Dispatch configuration file which connects to the
> master broker)
> Steps to reproduce the issue -
> 1. Start 2 artemis brokers with the provided master and slave broker xml files
> 2. Start the Qpid Dispatch router with the provided config file with frame
> trace on like this
> {noformat}
> PN_TRACE_FRM=1 qdrouterd -c failover.conf
> {noformat}
> 3. The master broker will send an open frame to the router than has a
> failover list. The open frame looks like the following -
> {noformat}
> [0x7f7b6000c1e0]:0 <- @open(16) [container-id="0.0.0.0",
> max-frame-size=4294967295, channel-max=65535, idle-time-out=30000,
> offered-capabilities=@PN_SYMBOL[:"sole-connection-for-container",
> :"DELAYED_DELIVERY", :"SHARED-SUBS", :"ANONYMOUS-RELAY"],
> properties={:product="apache-activemq-artemis",
> :"failover-server-list"=[{:hostname="127.0.0.1", :scheme="amqp", :port=62616,
> :"network-host"="127.0.0.1"}], :version="2.4.0"}]
> {noformat}
> Notice that the failover list is providing the url for the backup slave
> broker.
> 4. Now terminate the master broker.
> 5. Dispatch router must sense that the connection to the master broker has
> gone down and must try to connect to the slave broker but it does not.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
