You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2014/12/04 21:46:12 UTC
[jira] [Created] (PROTON-766) Proton-c Windows IO prints misleading
error messages
Chuck Rolke created PROTON-766:
----------------------------------
Summary: Proton-c Windows IO prints misleading error messages
Key: PROTON-766
URL: https://issues.apache.org/jira/browse/PROTON-766
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.8
Environment: Windows Server 2012 R2
Examples messaging c recv
Reporter: Chuck Rolke
Connecting to a port that is not open.
Windows:
{noformat}
> send -a [::1]
recv: No error
[0000000001241B10]:ERROR amqp:connection:framing-error SASL header mismatch: ''
CONNECTION ERROR connection aborted (remote)
send: No error
{noformat}
The same action on Linux:
{noformat}
> ./send -a [::1]
recv: Connection refused
[0x158d030]:ERROR amqp:connection:framing-error SASL header mismatch: Insufficient data to determine protocol [''] (connection aborted)
CONNECTION ERROR connection aborted (remote)
send: Broken pipe
{noformat}
The Linux messages are more useful and indicate the precise error conditions. The Windows messages show recv: and send: with 'No error' and that is not the case.
The same error message is displayed for IPv4 and IPv6.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)