[
https://issues.apache.org/jira/browse/THRIFT-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388756#comment-14388756
]
James E. King, III commented on THRIFT-2441:
--------------------------------------------
I would argue against allowing the client to hold the server in a particular
state. As it stands today in 0.9.2, someone can telnet to a thrift port and
leave it open, and prevent a thrift server from ever shutting down. It should
not be possible for the client to impose this level of control on the server.
The server should be the authority in stop behavior. I need to fix this in
order to upgrade a project using the older patch (first comment) and I am
starting on this today.
> 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: Roger Meier
>
> 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)
