Ganesh Murthy created DISPATCH-905:
--------------------------------------
Summary: 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
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
