[jira] [Commented] (PROTON-766) Proton-c Windows IO prints misleading error messages

["Chuck Rolke (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PROTON-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086227#comment-15086227 ] 

Chuck Rolke commented on PROTON-766:
------------------------------------

In reviewing this issue the behavior has changed. Now (master branch at commit 178aa46) there is no longer a misleading message. Instead the code fails silently.
{noformat}
W:\>send -a [::1]

W:\>
{noformat}

The failure is evident when proton trace is turned on
{noformat}
W:\>set PN_TRACE_FRM=1

W:\>send -a [::1]
[01216830]:  -> AMQP
[01216830]:0 -> @open(16) [container-id="C3540831-9767-4425-A13B-8769D12AF272", hostname="::1", channel-max=32767]
[01216830]:0 -> @begin(17) [next-outgoing-id=0, incoming-window=2147483647, outgoing-window=2147483647]
[01216830]:0 -> @attach(18) [name="sender-xxx", handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0, 
    source=@source(40) [durable=0, timeout=0, dynamic=false], 
    target=@target(41) [durable=0, timeout=0, dynamic=false], initial-delivery-count=0]
[01216830]:0 -> @close(24) [error=@error(29) [condition=:"amqp:connection:framing-error", 
    description="AMQP header mismatch: Insufficient data to determine protocol [''] (connection aborted)"]]
[01216830]:  <- EOS
{noformat}


> 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)