[ https://issues.apache.org/jira/browse/PROTON-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated PROTON-766: ------------------------------- Fix Version/s: (was: proton-c-0.19.0) proton-c-0.21.0 > 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 > Assignee: Cliff Jansen > Labels: windows > Fix For: proton-c-0.21.0 > > > 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.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org