You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2015/04/02 21:42:53 UTC
[jira] [Issue Comment Deleted] (THRIFT-2441) Cannot shutdown
TThreadedServer when clients are still connected
[ https://issues.apache.org/jira/browse/THRIFT-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James E. King, III updated THRIFT-2441:
---------------------------------------
Comment: was deleted
(was: After getting to TSimpleServer I see that I actually need to hook this right into the TServerSocket::interrupt() otherwise TSimpleServer would be blocked in recv on the TSocket and would wait for a client disconnect, so I will move it into interrupt.)
> Cannot shutdown TThreadedServer when clients are still connected
> ----------------------------------------------------------------
>
> Key: THRIFT-2441
> URL: https://issues.apache.org/jira/browse/THRIFT-2441
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.9.1
> Reporter: Chris Stylianou
> Assignee: Ben Craig
>
> When calling stop() on the TThreadedServer no interrupts are sent to the client threads. This means the stop() call blocks on tasksMonitor.wait() until all client naturally disconnect.
> How can we tell the client thread connections to close/exit during the TThreadedServer::stop() call?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)