[
https://issues.apache.org/jira/browse/THRIFT-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681366#comment-16681366
]
Allen George commented on THRIFT-4451:
--------------------------------------
!Screen Shot 2018-11-09 at 07.03.39.png!
Here's a representative sample of what I'm seeing. Specifically, after the call
to the second-test server is sent and the server responds with an {{ACK}}, the
client immediately sends out a {{FIN}}. Now, once the server sends its response
the client thinks the connection is dead, and so of course nothing is read.
AFAICT, I'm not invoking {{shutdown()}} explicitly, neither is {{Drop}} on the
{{TcpStream}} getting called.
> Rust client fails to communicate with multiplexed perl/c_glib servers
> ---------------------------------------------------------------------
>
> Key: THRIFT-4451
> URL: https://issues.apache.org/jira/browse/THRIFT-4451
> Project: Thrift
> Issue Type: Bug
> Components: Rust - Library
> Reporter: Allen George
> Assignee: Allen George
> Priority: Major
> Attachments: Screen Shot 2018-11-09 at 07.03.39.png
>
>
> As stated in description. Minimal case is to comment out everything in the
> Rust {{test_client}} leaving only the {{SecondService}} call behind.
> From what I can tell the Rust socket isn't getting *any* bytes at all for the
> response (i.e. it can't even get the first 4 bytes of the message header).
> There is a {{flush()}} call on the remote side - so that's puzzling.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
