[jira] [Comment Edited] (THRIFT-2441) Cannot shutdown TThreadedServer when clients are still connected

["James E. King, III (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390576#comment-14390576 ] 

James E. King, III edited comment on THRIFT-2441 at 4/1/15 1:56 PM:
--------------------------------------------------------------------

[~roger.meier] the patch that was pulled in providing stop() inside TThreadedServer.cpp works against 0.8.0 (although incorrect as this discussion shows) but against 0.9.2, TThreadedServer.h provides stop() so this won't even compile.  It should be backed out, pending a working solution folks agree is acceptable.


was (Author: jking3):
[~roger.meier] the patch that was pulled in providing stop() inside TThreadedServer.cpp works against 0.8.0 but against 0.9.2, TThreadedServer.h provides stop() so this won't even compile.  It should be backed out, pending a working solution folks agree is acceptable.

> 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)