[THRIFT-2441] Cannot shutdown TThreadedServer when clients are still connected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.1
• Fix Version/s: 0.9.3
• Component/s: C++ - Library
• Assignee: James E. King III
• Reporter: Chris Stylianou
• Created: 02/Apr/14 09:05
• Updated: 01/Feb/19 05:44
• Resolved: 24/Apr/15 13:59

Description

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?

Issue Links

• blocks: THRIFT-3081 C++ Consolidate client processing loops in TServers
• is duplicated by: THRIFT-3447 Cannot shutdown TThreadPoolServer when clients are still connected
• is duplicated by: THRIFT-2099 Stop TThreadPoolServer with alive connections.
• is related to: THRIFT-3590 TPipeServer: stop() does not work when clients are connected
• is related to: THRIFT-3061 C++ TSSLSocket shutdown delay/vulnerability
• is related to: THRIFT-3970 Server does not limititate client connections
• relates to: THRIFT-4500 Unable to stop socket server while there are connected clients
• relates to: THRIFT-4252 Cannot shutdown Java server when clients are still connected