[
https://issues.apache.org/jira/browse/THRIFT-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407862#comment-16407862
]
Allen George commented on THRIFT-4451:
--------------------------------------
Weirdly enough, here's the sequence of back and forth. The perl server is
listening on 45773
{noformat}
<---- REQUEST
12:48:59.775728 IP (tos 0x0, ttl 64, id 57597, offset 0, flags [DF], proto TCP
(6), length 113)
[6/1830]
127.0.0.1.52408 > 127.0.0.1.45773: Flags [P.], cksum 0xfe65 (incorrect ->
0xa11f), seq 1:62, ack 1, win 342, options [nop,nop,TS val 6743292 ecr
6743292], length 61
E..q..@.@.[.............N...zu.....V.e.....
.f...f..........SecondService:secondtestString...........test_string.
WHAT IS THIS?!
12:48:59.775740 IP (tos 0x0, ttl 64, id 14716, offset 0, flags [DF], proto TCP
(6), length 52)
127.0.0.1.45773 > 127.0.0.1.52408: Flags [.], cksum 0xfe28 (incorrect ->
0x81e0), seq 1, ack 62, win 342, options [nop,nop,TS val 6743292 ecr 6743292],
length 0
E..49|@.@..F............zu..N..E...V.(.....
.f...f..
WHAT IS THIS?
12:49:05.748396 IP (tos 0x0, ttl 64, id 57598, offset 0, flags [DF], proto TCP
(6), length 52)
127.0.0.1.52408 > 127.0.0.1.45773: Flags [F.], cksum 0xfe28 (incorrect ->
0x7f89), seq 62, ack 1, win 342, options [nop,nop,TS val 6743890 ecr 6743292],
length 0
E..4..@.@.[.............N..Ezu.....V.(.....
.f.R.f..
---> RESPONSE
12:49:05.752416 IP (tos 0x0, ttl 64, id 14717, offset 0, flags [DF], proto TCP
(6), length 126)
127.0.0.1.45773 > 127.0.0.1.52408: Flags [P.], cksum 0xfe72 (incorrect ->
0x2820), seq 1:75, ack 63, win 342, options [nop,nop,TS val 6743890 ecr
6743890], length 74
E..~9}@.@...............zu..N..F...V.r.....
{noformat}
I'm assuming the "WHAT IS THIS" lines are TCP-level packets?
> 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
>
> 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)
