[DISPATCH-184] dispatch do not stop when 'amqp' is not defined

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Not A Bug
• Component/s: Container

Environment

Gentoo linux, Linux falka 4.2.3-gentoo #1 SMP Thu Oct 8 10:08:43 CEST 2015 x86_64 Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz GenuineIntel GNU/Linux

proton-c (latest from apache github a16c58a59c2a5504ecd556dd397b7d28cc68dbd4)
dispatch (latest from apache github 8353ac674a7150a1bbfa63c912ad9689a492e84a)

sys-devel/gcc-4.9.3
dev-lang/python-2.7.10

• Assignee: Unassigned
• Reporter: Zdenek Kraus
• Created: 21/Oct/15 14:17
• Updated: 02/Oct/19 17:54
• Resolved: 15/Jun/16 14:06

Description

If there is no existent record of 'amqp' protocol being 5672/tcp in /etc/services, dispatch logs error messages and continue on.

steps:
1. make sure that record 'amqp 5672/tcp' is not present at /etc/services
2. run qpid dispatch

current results:
Wed Oct 21 16:11:35 2015 DRIVER (error) getaddrinfo(0.0.0.0, amqp): Servname not supported for ai_socktype
and continue.

expected:
error message and should stop with error.

note: this could be added into documentation

Issue Links

• links to: GitHub Pull Request #82