You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/22 12:31:02 UTC
[jira] [Commented] (THRIFT-4340) Erlang fix a crash on client close
[ https://issues.apache.org/jira/browse/THRIFT-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176338#comment-16176338 ]
ASF GitHub Bot commented on THRIFT-4340:
----------------------------------------
Github user jeking3 commented on the issue:
https://github.com/apache/thrift/pull/1367
I opened THRIFT-4340 for you on this.
> Erlang fix a crash on client close
> ----------------------------------
>
> Key: THRIFT-4340
> URL: https://issues.apache.org/jira/browse/THRIFT-4340
> Project: Thrift
> Issue Type: Bug
> Components: Erlang - Library
> Affects Versions: 0.10.0
> Reporter: James E. King, III
> Assignee: James E. King, III
> Fix For: 0.11.0
>
>
> When a client closes a connection to a framed server the server was
> crashing because the fact that the transport was framed was being
> lost. Looking through the file I noticed that the block from lines
> 87-95, looked different from the one from 59-66. The culprit was
> that when an error was occuring in the 59-66 block it was being
> propagated up without rewrapping. That would cause a failure
> much further up the chain.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)