[DISPATCH-261] Bind error on one port causes bind error on other ports

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: 0.6.0
• Assignee: Ganesh Murthy
• Reporter: Charles E. Rolke
• Created: 05/Apr/16 22:06
• Updated: 02/Oct/19 17:55
• Resolved: 19/Apr/16 18:18

Description

Run a service, like an AMQP broker, on port 5672.

Start Dispatch Router with config

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

listener {
    addr: 0.0.0.0
    port: 20102
}

The router reports:

Tue Apr  5 17:55:04 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp proto=any role=normal
Tue Apr  5 17:55:04 2016 DRIVER (error) bind: Address already in use
Tue Apr  5 17:55:04 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20102 proto=any role=normal
Tue Apr  5 17:55:04 2016 DRIVER (error) bind: Address already in use

The error on port 5672 is correct. The error on port 20102 is bogus. There is no conflict on that port.