[DISPATCH-804] connectors ignore addr

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0
• Assignee: Ganesh Murthy
• Reporter: Gordon Sim
• Created: 11/Aug/17 15:30
• Updated: 20/Nov/17 18:33
• Resolved: 11/Aug/17 16:11

Description

The addr field of connector appears to be entirely ignored, with 127.0.0.1 used instead. E.g. with the following config:

router {
    mode: standalone
    routerId: myrouter
}

listener {
    addr: 0.0.0.0
    port: amqp
    authenticatePeer: no
}

connector {
    name: myconnector
    addr: google.com
    port: 5673
}

you see

2017-08-11 16:27:13.184 +0100 AGENT (warning) routerId is deprecated, use id instead
2017-08-11 16:27:13.555 +0100 SERVER (warning) HTTP support is not available
2017-08-11 16:27:13.563 +0100 SERVER (info) Container Name: myrouter
2017-08-11 16:27:13.651 +0100 ROUTER (info) Router started in Standalone mode
2017-08-11 16:27:13.679 +0100 ROUTER_CORE (info) Allow Unsettled Multicast: no
2017-08-11 16:27:13.1033 +0100 ROUTER_CORE (info) Router Core thread running. 0/myrouter
2017-08-11 16:27:13.1049 +0100 ROUTER_CORE (info) In-process subscription M/$management
2017-08-11 16:27:13.7044 +0100 AGENT (info) Activating management agent on $_management_internal
2017-08-11 16:27:13.7099 +0100 ROUTER_CORE (info) In-process subscription L/$management
2017-08-11 16:27:13.7122 +0100 ROUTER_CORE (info) In-process subscription L/$_management_internal
2017-08-11 16:27:13.7410 +0100 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp proto=any, role=normal
2017-08-11 16:27:13.8007 +0100 CONN_MGR (info) Configured Connector: 127.0.0.1:5673 proto=any, role=normal    <----- NOTE: Wrong hostname!!
2017-08-11 16:27:13.8460 +0100 POLICY (info) Policy configured maxConnections: 65535, policyDir: '', access rules enabled: 'false'
2017-08-11 16:27:13.9149 +0100 POLICY (info) Policy fallback defaultVhost is defined: '$default'
2017-08-11 16:27:13.9175 +0100 SERVER (notice) Operational, 4 Threads Running (process ID 3236)
2017-08-11 16:27:13.9286 +0100 SERVER (notice) Listening on 0.0.0.0:amqp

And indeed it connects to a broker on the local host.