You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2014/02/25 04:32:19 UTC

[jira] [Resolved] (KAFKA-1279) SocketServer.shutdown() doesn't close open connections

     [ https://issues.apache.org/jira/browse/KAFKA-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Kreps resolved KAFKA-1279.
------------------------------

    Resolution: Fixed

> SocketServer.shutdown() doesn't close open connections
> ------------------------------------------------------
>
>                 Key: KAFKA-1279
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1279
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jay Kreps
>            Assignee: Jay Kreps
>         Attachments: KAFKA-1279.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)