[
https://issues.apache.org/jira/browse/THRIFT-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509980#comment-17509980
]
Plumet commented on THRIFT-5499:
--------------------------------
There are a couple of solutions to this problem:
# Keep reading synchronously from the underlying stream and let the
configuration of the clients change (AllowSynchronousIO).
# Read asynchronously from the steam and use a timer and create a
timeoutexception.
# Remove the receive timeout in the configuration as it's not supported on
asynchronous read operations.
> Receive timeout not triggered when response exceeds timeout
> -----------------------------------------------------------
>
> Key: THRIFT-5499
> URL: https://issues.apache.org/jira/browse/THRIFT-5499
> Project: Thrift
> Issue Type: Bug
> Components: netstd - Library
> Affects Versions: 0.15.0, 0.16.0
> Reporter: Plumet
> Assignee: Plumet
> Priority: Major
> Attachments: THRIFT-ReceiveTimeout.zip
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When the client's timeout is set to valid value and the response exceeds this
> timeout there is no exception thrown.
> I've provided a reproducible testcase[^THRIFT-ReceiveTimeout.zip].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
