[
https://issues.apache.org/jira/browse/THRIFT-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932682#comment-16932682
]
Dedipyaman Das edited comment on THRIFT-4958 at 9/18/19 5:10 PM:
-----------------------------------------------------------------
[~q.xu]While debugging the issue I played with the timeout and finally turned
my read timeout upto 20 seconds and yet it doesn't seem to make a difference.
What I did notice was it works for a certain number of requests and stops
working. It also stops working if I am being to quick to send the requests (it
could be because it may have the certain number of requests its failing for),
however I see no errors at the server side.
Java (Server) logs nothing, PHP (client) logs the read timeout . I have also
tried changing the server type from TThreadSelectorServer to THsHaServer and
still nothing.
was (Author: dedipyaman):
[~q.xu]While debugging the issue I played with the timeout and finally turned
my read timeout upto 20 seconds and yet it doesn't seem to make a difference.
What I did notice was it works for a certain number of requests and stops
working. It also stops working if I am being to quick to send the requests (it
could be because it may have the certain number of requests its failing for),
however I see no errors at the server side.
Java (Server) logs nothing, PHP (client) logs the read timeout .
> 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)
