You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/25 07:33:00 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=16375976#comment-16375976 ] 

ASF GitHub Bot commented on KAFKA-3986:
---------------------------------------

hachikuji closed pull request #1657: KAFKA-3986 Add null check to completedReceives
URL: https://github.com/apache/kafka/pull/1657
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>            Priority: Major
>             Fix For: 1.0.0
>
>
> 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
(v7.6.3#76005)