[
https://issues.apache.org/jira/browse/THRIFT-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696306#comment-16696306
]
ASF GitHub Bot commented on THRIFT-4671:
----------------------------------------
BoringKen opened a new pull request #1635: THRIFT-4671: handle client's
unexpected close.
URL: https://github.com/apache/thrift/pull/1635
THRIFT-9999: handle client's unexpected close. Avoid the server work thread
falling into dead loop.
Client: c_glib
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> c glib is unable to handle client close unexpectedly
> ----------------------------------------------------
>
> Key: THRIFT-4671
> URL: https://issues.apache.org/jira/browse/THRIFT-4671
> Project: Thrift
> Issue Type: Bug
> Components: C glib - Library
> Affects Versions: 0.11.0
> Environment: ubuntu 16.04
> thrift sever: c_glib
> thrift client: c_glib, go
> Reporter: lixiasong
> Priority: Major
> Labels: easyfix, ready-to-commit
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When using c_glib thrift server. Once a client connects to the server *but
> does nothing (didn't send data to server) when being connected*. If the
> client closed unexpectedly(such as being killed) at the moment, *the
> thrift-work thread for that client wont't be closed* and read the closed
> client sock fd in the server forever.
> *I*t has been fixed in my branch, and will be tested and committed later if
> it runs well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
