[
https://issues.apache.org/jira/browse/PROTON-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409106#comment-16409106
]
ASF subversion and git services commented on PROTON-1357:
---------------------------------------------------------
Commit 70c8ac833cdb831f5e88606729217d890279120c in qpid-proton's branch
refs/heads/master from Ji?? Dan?k
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=70c8ac8 ]
PROTON-1357 add reproducer to fuzzing corpus for regression testing
> Example C clients do not disconnect on protocol errors
> ------------------------------------------------------
>
> Key: PROTON-1357
> URL: https://issues.apache.org/jira/browse/PROTON-1357
> Project: Qpid Proton
> Issue Type: Bug
> Components: examples, proton-c
> Affects Versions: 0.16.0
> Reporter: Jiri Daněk
> Assignee: Alan Conway
> Priority: Major
> Fix For: proton-c-0.18.0
>
> Attachments: leak-f1c681da874efe3b168d6bd00e1de53c5a3823ea
>
>
> If you take {{libuv_recv}} example C program and set up a "server" with
> {{$ nc -l 5672 < leak-f1c681da874efe3b168d6bd00e1de53c5a3823ea}}
> and then run
> {noformat}
> $ ./libuv_recv -a 127.0.0.1:5672/jms.queue.example
> [0x69ab390]:Error decoding frame: PN_UNDERFLOW not enough data to decode
> \x00S\x12\xc04\x0a\xa1\x0bmy_receiverCBP\x02\x00\x00\x00S(\xc0\x14\x01\xa1\x11jms.queue.example\x00S)E@BC
> {noformat}
> then {{libuv_recv}} does not quit even after I kill the "server" with ^C
> (which should close the socket). This happens with all C example receivers.
> It does not happen with {{examples/python/simple_recv}}, which just
> disconnects and then keeps trying to reconnect. I am not sure if the
> disconnect behavior is just missing from the C clients (in that case it is
> not a big deal) or if it gets stuck somewhere deeper in proton-c (in which
> case it may actually impact someone).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
