kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wupeng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-2353) SocketServer.Processor should catch exception and close the socket properly in configureNewConnections.
Date Wed, 21 Jun 2017 07:42:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057099#comment-16057099
] 

wupeng commented on KAFKA-2353:
-------------------------------

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)

Mime
View raw message