You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Dan (JIRA)" <ji...@apache.org> on 2017/07/13 06:46:00 UTC

[jira] [Created] (KAFKA-5587) Processor got uncaught exception: NullPointerException

Dan created KAFKA-5587:
--------------------------

             Summary: Processor got uncaught exception: NullPointerException
                 Key: KAFKA-5587
                 URL: https://issues.apache.org/jira/browse/KAFKA-5587
             Project: Kafka
          Issue Type: Bug
          Components: core
    Affects Versions: 0.10.1.1
            Reporter: Dan


[2017-07-12 21:56:39,964] ERROR Processor got uncaught exception. (kafka.network.Processor)
java.lang.NullPointerException
        at kafka.network.Processor$$anonfun$processCompletedReceives$1.apply(SocketServer.scala:490)
        at kafka.network.Processor$$anonfun$processCompletedReceives$1.apply(SocketServer.scala:487)
        at scala.collection.Iterator$class.foreach(Iterator.scala:727)
        at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
        at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
        at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
        at kafka.network.Processor.processCompletedReceives(SocketServer.scala:487)
        at kafka.network.Processor.run(SocketServer.scala:417)
        at java.lang.Thread.run(Thread.java:745)

Anyone knows the cause of this exception? What's the effect of it? 
When this exception occurred, the log also showed that the broker was frequently shrinking ISR to itself. Are these two things interrelated?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)