You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2019/08/01 16:55:01 UTC

[jira] [Commented] (KAFKA-8731) InMemorySessionStore throws NullPointerException on startup

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

Guozhang Wang commented on KAFKA-8731:
--------------------------------------

Let's see how many blockers we have accumulated for 2.3.1 so far to decide whether we should get a release out sooner than later.

> InMemorySessionStore throws NullPointerException on startup
> -----------------------------------------------------------
>
>                 Key: KAFKA-8731
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8731
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.3.0
>            Reporter: Jonathan Gordon
>            Assignee: Sophie Blee-Goldman
>            Priority: Blocker
>             Fix For: 2.4.0, 2.3.1
>
>
> I receive a NullPointerException on startup when trying to use the new InMemorySessionStore via Stores.inMemorySessionStore(...) using the DSL.
> Here's the stack trace:
> {{ERROR [2019-07-29 21:56:52,246] org.apache.kafka.streams.processor.internals.StreamThread: stream-thread [trace_indexer-c8439020-12af-4db2-ad56-3e58cd56540f-StreamThread-1] Encountered the following error during processing:}}
> {{! java.lang.NullPointerException: null}}
> {{! at org.apache.kafka.streams.state.internals.InMemorySessionStore.remove(InMemorySessionStore.java:123)}}
> {{! at org.apache.kafka.streams.state.internals.InMemorySessionStore.put(InMemorySessionStore.java:115)}}
> {{! at org.apache.kafka.streams.state.internals.InMemorySessionStore.lambda$init$0(InMemorySessionStore.java:93)}}
> {{! at org.apache.kafka.streams.processor.internals.StateRestoreCallbackAdapter.lambda$adapt$1(StateRestoreCallbackAdapter.java:47)}}
> {{! at org.apache.kafka.streams.processor.internals.CompositeRestoreListener.restoreBatch(CompositeRestoreListener.java:89)}}
> {{! at org.apache.kafka.streams.processor.internals.StateRestorer.restore(StateRestorer.java:92)}}
> {{! at org.apache.kafka.streams.processor.internals.StoreChangelogReader.processNext(StoreChangelogReader.java:317)}}
> {{! at org.apache.kafka.streams.processor.internals.StoreChangelogReader.restore(StoreChangelogReader.java:92)}}
> {{! at org.apache.kafka.streams.processor.internals.TaskManager.updateNewAndRestoringTasks(TaskManager.java:328)}}
> {{! at org.apache.kafka.streams.processor.internals.StreamThread.runOnce(StreamThread.java:867)}}
> {{! at org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:805)}}
> {{! at org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:774)}}
>  
> Here's the Slack thread:
> [https://confluentcommunity.slack.com/archives/C48AHTCUQ/p1564438647169600]
>  
> Here's a current PR aimed at fixing the issue:
> [https://github.com/apache/kafka/pull/7132]
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)