[
https://issues.apache.org/jira/browse/THRIFT-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386646#comment-14386646
]
James E. King, III commented on THRIFT-2441:
--------------------------------------------
I believe this change is an improvement for the reason Randy suggested - this
is analogous to a network disconnect, and all Thrift based implementations that
require idempotent behavior must already account for that, therefore this
change imposes no additional requirements on any implementation.
One could certainly file an enhancement request to change stop to take a
{{const boost::posix_time::time_duration&}} so that the caller can decide how
long to wait for the open handler requests to complete if folks want the
ability to control this. That would not be difficult to do.
> 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)
