[
https://issues.apache.org/jira/browse/THRIFT-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927531#comment-16927531
]
Jose Andres Gomez Tovar edited comment on THRIFT-4958 at 9/19/19 9:31 AM:
--------------------------------------------------------------------------
I have a similar c ++ server / client environment.
The c ++ client calls a method (attributeDefinitionsAliases) and waits for a
response.
The c ++ server starts writing to the socket but locks. See attached screenshot
of a Wireshark capture.
After closing the c ++ client on the c ++ server, an exception appears:
Thrift internal message: TSocket::write_partial() send() <Host:
fe80::ccad:c9f2:4f6d:341c%3 Port: 50396>: errno = 10054
Thrift internal message: TConnectedClient died: write() send(): errno = 10054
{color:red}EDIT 1:{color}
It is not a thrift problem. It seems a problem with the way the server
starts/launch. I have an application (launcher-app) that starts/launch the
server with QProcess (https://doc.qt.io/archives/qt-4.8/qprocess.html), using
popen *works fine*.
was (Author: jose andres):
I have a similar c ++ server / client environment.
The c ++ client calls a method (attributeDefinitionsAliases) and waits for a
response.
The c ++ server starts writing to the socket but locks. See attached screenshot
of a Wireshark capture.
After closing the c ++ client on the c ++ server, an exception appears:
Thrift internal message: TSocket::write_partial() send() <Host:
fe80::ccad:c9f2:4f6d:341c%3 Port: 50396>: errno = 10054
Thrift internal message: TConnectedClient died: write() send(): errno = 10054
> TSocket: timed out reading 4 bytes from server:port
> ----------------------------------------------------
>
> Key: THRIFT-4958
> URL: https://issues.apache.org/jira/browse/THRIFT-4958
> Project: Thrift
> Issue Type: Bug
> Components: PHP - Library
> Affects Versions: 0.12.0
> Environment: Thrift 0.12: PHP 7.3 with Apache 2.4 on Ubuntu 18.04 ,
> Oracle JDK 8
> Reporter: Dedipyaman Das
> Priority: Critical
> Labels: bug
> Attachments: e.bmp
>
>
> I have come this error across on my development server while working on a PHP
> 7.3 client and Java 8 Server.
> *TSocket: timed out reading 4 bytes from server*:port
> The PHP client is using TFramedTransport with Binary Protocol and the Java
> server is using TThreadSelectorServer. The error appeared all of a sudden and
> doesn't go away unless I restart the server, and it comes back after a while.
> This issue seems to have been raised at:
> https://issues.apache.org/jira/browse/THRIFT-347 and fixed for version 0.6,
> but it seems to occur for me on version 0.12 - for reasons I don't know.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
