[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels
[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3986: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > 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.11.1.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 (v6.3.15#6346)
[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels
[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3986: - Fix Version/s: (was: 0.10.1.1) (was: 0.10.0.2) 0.10.2.0 > 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.2.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 (v6.3.4#6332)
[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels
[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3986: --- Fix Version/s: 0.10.1.1 > 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)
[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels
[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3986: --- Fix Version/s: (was: 0.10.0.1) 0.10.0.2 > 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 > > > 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)
[jira] [Updated] (KAFKA-3986) completedReceives can contain closed channels
[ https://issues.apache.org/jira/browse/KAFKA-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3986: --- Fix Version/s: 0.10.0.1 > 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.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)
