You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/11/02 06:16:58 UTC
[jira] [Commented] (KAFKA-3986) completedReceives can contain
closed channels
[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15627907#comment-15627907 ]
Jason Gustafson commented on KAFKA-3986:
----------------------------------------
I think this is handled in the patch for KAFKA-3703: https://github.com/apache/kafka/pull/1836/.
> completedReceives can contain closed channels
> ----------------------------------------------
>
> Key: KAFKA-3986
> URL: https://issues.apache.org/jira/browse/KAFKA-3986
> Project: Kafka
> Issue Type: Bug
> Components: network
> Reporter: Ryan P
> Fix For: 0.10.0.2, 0.10.1.1
>
>
> I'm not entirely sure why at this point but it is possible to throw a Null Pointer Exception when processingCompletedReceives. This happens when a fairly substantial number of simultaneously initiated connections are initiated with the server.
> The processor thread does carry on but it may be worth investigating how the channel could be both closed and completedReceives.
> The NPE in question is thrown here:
> https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/network/SocketServer.scala#L490
> It can not be consistently reproduced either.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)