You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "wupeng (JIRA)" <ji...@apache.org> on 2017/06/21 07:56:02 UTC
[jira] [Comment Edited] (KAFKA-2353) SocketServer.Processor should
catch exception and close the socket properly in configureNewConnections.
[ https://issues.apache.org/jira/browse/KAFKA-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057099#comment-16057099 ]
wupeng edited comment on KAFKA-2353 at 6/21/17 7:55 AM:
--------------------------------------------------------
Excuse me sir. What is the Affects Version of this patch?
I have the same error just like you, so I want to try this patch.
was (Author: wupppgg@gmail.com):
Excuse me buddy. Which is the Affects Version of this patch?
I have the same error just like you, so I want to try this patch.
> SocketServer.Processor should catch exception and close the socket properly in configureNewConnections.
> -------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-2353
> URL: https://issues.apache.org/jira/browse/KAFKA-2353
> Project: Kafka
> Issue Type: Bug
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Fix For: 0.9.0.0
>
> Attachments: KAFKA-2353_2015-07-21_22:02:24.patch, KAFKA-2353_2015-07-22_17:51:42.patch, KAFKA-2353.patch
>
>
> We see an increasing number of sockets in CLOSE_WAIT status in our production environment in recent couple of days. From the thread dump it seems one of the Processor thread has died but the acceptor was still putting many new connections its new connection queue.
> The cause of dead Processor thread was due to we are not catching all the exceptions in the Processor thread. For example, in our case it seems to be an exception thrown in configureNewConnections().
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)