[
https://issues.apache.org/jira/browse/PROTON-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17253031#comment-17253031
]
Clifford Jansen commented on PROTON-2313:
-----------------------------------------
Perhaps this is a test environment problem as Jiri suggested?
In both cases it appears that Dispatch is doing the reconnecting, not Proton.
In both cases Proton is returning an error. In the "good" case, Proton is
reporting that the connection failed because the name resolving step failed. In
the "bad" case, Proton is reporting that name resolution never happened. In
each case Proton gives up because it has nowhere to connect to.
If DNS is broken, I'm not sure there is much value in running the test.
> [proton-c] Connection to unresolvable address returns retry instead of failure
> ------------------------------------------------------------------------------
>
> Key: PROTON-2313
> URL: https://issues.apache.org/jira/browse/PROTON-2313
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: proton-c-0.33.0
> Reporter: Charles E. Rolke
> Priority: Major
>
> A qpid-dispatch self test tries to open a connector (outgoing connection) to
> an unresolvable address.
> [https://github.com/apache/qpid-dispatch/blob/0634a070aa6f902bf5b6f9537a5406e4cfc5a0d5/tests/system_tests_bad_configuration.py#L105]
> The expectation is that proton will return a proton:io error. This does not
> appear to be a regression as the issue exists in 0.33.0.
> {code:java}
> Fedora 31 64-bit bare metal
> Proton git branch master @ e4c179855. Dispatch git branch master @ 0634a070
> 2020-12-21 11:04:51.294685 -0500 SERVER (trace) [C1] Connecting to
> unresolvable.host.name:amqp (/home/chug/git/qpid-dispatch/src/server.c:1204)
> 2020-12-21 11:04:51.555518 -0500 SERVER (info) [C1] Connection to
> unresolvable.host.name:amqp failed: proton:io Name or service not known -
> connect to unresolvable.host.name:5672
> (/home/chug/git/qpid-dispatch/src/server.c:1065)
> {code}
> In some cases proton never returns an error but retries indefinitely.
> {code:java}
> Host: Fedora 32 x86_64
> VM: whatever one gets from qpid-dispatch/dockerfiles/Dockerfile-fedora
> in VM uname -a shows: Linux 879605af38a6 5.9.14-100.fc32.x86_64 #1 SMP
> Fri Dec 11 14:30:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
> 2020-12-21 15:53:46.738685 +0000 SERVER (trace) [C1] Connecting to
> unresolvable.host.name:amqp (/main/qpid-dispatch/src/server.c:1204)
> 2020-12-21 15:53:46.919237 +0000 SERVER (info) [C1] Connection to
> unresolvable.host.name:amqp failed: proton:io Temporary failure in name
> resolution - connect to unresolvable.host.name:5672
> (/main/qpid-dispatch/src/server.c:1065)
> 2020-12-21 15:53:51.919149 +0000 SERVER (trace) [C2] Connecting to
> unresolvable.host.name:amqp (/main/qpid-dispatch/src/server.c:1204)
> 2020-12-21 15:53:52.107100 +0000 SERVER (info) [C2] Connection to
> unresolvable.host.name:amqp failed: proton:io Temporary failure in name
> resolution - connect to unresolvable.host.name:5672
> (/main/qpid-dispatch/src/server.c:1065)
> 2020-12-21 15:53:57.108089 +0000 SERVER (trace) [C3] Connecting to
> unresolvable.host.name:amqp (/main/qpid-dispatch/src/server.c:1204)
> 2020-12-21 15:53:57.247889 +0000 SERVER (info) [C3] Connection to
> unresolvable.host.name:amqp failed: proton:io Temporary failure in name
> resolution - connect to unresolvable.host.name:5672
> (/main/qpid-dispatch/src/server.c:1065)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
