You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Zdenek Kraus (JIRA)" <ji...@apache.org> on 2015/10/21 16:18:27 UTC

[jira] [Created] (DISPATCH-184) dispatch do not stop when 'amqp' is not defined

Zdenek Kraus created DISPATCH-184:
-------------------------------------

             Summary: dispatch do not stop when 'amqp' is not defined
                 Key: DISPATCH-184
                 URL: https://issues.apache.org/jira/browse/DISPATCH-184
             Project: Qpid Dispatch
          Issue Type: Bug
          Components: 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

            Reporter: Zdenek Kraus
            Priority: Minor


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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org