[
https://issues.apache.org/jira/browse/THRIFT-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108576#comment-18108576
]
Dmytro Shteflyuk commented on THRIFT-2301:
------------------------------------------
Unable to reproduce the reported ProtocolException.
A plain peer disconnect through Thrift::Socket raises
Thrift::TransportException ("end of file reached") on both the reported 0.9.1
release and current master. On 0.9.1, IOStreamTransport instead fails with
NoMethodError on a nil read;
[THRIFT-6144|https://issues.apache.org/jira/browse/THRIFT-6144] fixed that
separate behavior.
[THRIFT-1911|https://issues.apache.org/jira/browse/THRIFT-1911] changed
operations on an already-closed socket from IOError to TransportException, but
neither that change nor THRIFT-6144 explains the ProtocolException reported
here. No commit or pull request references THRIFT-2301, and the report does not
include the transport/protocol stack, exception message or backtrace, or
disconnect timing needed to reconstruct another trigger.
Closing as Cannot Reproduce.
> [ruby] socket closed but throw ProtocolException
> ------------------------------------------------
>
> Key: THRIFT-2301
> URL: https://issues.apache.org/jira/browse/THRIFT-2301
> Project: Thrift
> Issue Type: Improvement
> Components: Ruby - Library
> Affects Versions: 0.9.1
> Reporter: ted wang
> Priority: Minor
>
> I test kill thrift server when client running, and found a ProtocolException
> be thrown, why not TransportException?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
