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/03/26 22:26:54 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14382706#comment-14382706 ]
James E. King, III commented on THRIFT-2441:
--------------------------------------------
I can verify the fix posted on 04/Apr/14 does resolve this issue as we experienced this issue and we have been using this fix for a long time. It is actually present back to at least 0.8.0.
> 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
>
> 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)