[ https://issues.apache.org/jira/browse/THRIFT-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491324#comment-14491324 ]
ASF GitHub Bot commented on THRIFT-2441: ---------------------------------------- Github user jeking3 commented on the pull request: https://github.com/apache/thrift/pull/424#issuecomment-91989278 As part of work on THRIFT-3084 I added a TServer integration test, and found that the shutdown behavior and the rules for when you can call setInterruptableChildren() had to be tightened up for a couple cases. I am going to close this pull request until this is resolved so that it doesn't get merged in until the test passes. > 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 > Attachments: THRIFT-2441-prelim.patch > > > 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)