Affects Version/s: None
Fix Version/s: None
SocketServer.shutdown() stops the selector thread but doesn't actually close all the existing connections.
In normal operations this doesn't matter much because right after shutting down the socket server the process exits which closes all the connections. However we found this issue during unit testing--essentially we are leaking all the connections so shutdown() doesn't actually cause any error at all on the client which is still able to write to the socket and just never receives a response.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|8h 22m||1||Jay Kreps||25/Feb/14 03:31|
|Workflow||Apache Kafka Workflow [ 13052690 ]||no-reopen-closed, patch-avail [ 13055340 ]|
|Workflow||no-reopen-closed, patch-avail [ 12844101 ]||Apache Kafka Workflow [ 13052690 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|