[
https://issues.apache.org/jira/browse/PROTON-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318611#comment-14318611
]
Rafael H. Schloming commented on PROTON-804:
--------------------------------------------
I checked the fix and it does indeed avoid the busy loop.
Regarding your comments on the test, it does assume an implementation behavior,
but I'm not sure why that is a problem. It's not a general purpose interop
test, it only ever runs (or could possibly be run) against either the proton-c
or proton-j implementation. If what you're saying is that you want to choose a
different behavior, that's fine, but I would still expect that we test for
whatever we decide the appropriate choice is, i.e. modify the test to check
that the server sends back EOS immediately instead of sending back an error.
> the transport doesn't always shutdown its output properly
> ---------------------------------------------------------
>
> Key: PROTON-804
> URL: https://issues.apache.org/jira/browse/PROTON-804
> Project: Qpid Proton
> Issue Type: Bug
> Reporter: Rafael H. Schloming
> Assignee: Andrew Stitcher
> Attachments:
> 0001-This-may-be-a-fix-for-PROTON-804-on-error-in-server-.patch,
> transport-test.patch
>
>
> I believe the issue is related to the autodetect code andrew added not too
> long ago. I've attached a patch that has a test case with a relatively
> minimal reproducer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
