[
https://issues.apache.org/jira/browse/IGNITE-14439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402637#comment-17402637
]
Pavel Vinokurov commented on IGNITE-14439:
------------------------------------------
Hi [~francopo], most probably NPE was caused by another issue because before
calling GridServiceProcessor.onKernalStart the system cache should be
initialised. Is those NPE being repeated all the time?
> NPE when accessing clustername before first exchange finished
> -------------------------------------------------------------
>
> Key: IGNITE-14439
> URL: https://issues.apache.org/jira/browse/IGNITE-14439
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.9
> Reporter: Pavel Vinokurov
> Assignee: Pavel Vinokurov
> Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [IGNITE-11406|https://issues.apache.org/jira/browse/IGNITE-11406] has not
> been fixed properly for two reasons. The first is one is that
> _GridCacheProcessor.utilityCache_ could be accessed before the first exchange
> finished. The second is that it doesn't resolve the original issue, because
> _GridServiceProcessor.onKernelStop_ is followed by
> _GridCacheProcessor.onKernelStop_, so caches should be already initialized.
> Thus that fix should be reverted.
> Revering this fix induces the issue related to accessing the utility cache by
> getting cluster name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
