[
https://issues.apache.org/jira/browse/IGNITE-14439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312172#comment-17312172
]
Ignite TC Bot commented on IGNITE-14439:
----------------------------------------
{panel:title=Branch: [pull/8944/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8944/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 9{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5940025]]
* {color:#013220}IgniteCacheTestSuite9:
ClusterNameBeforeActivation.testGetClusterNameBeforeSystemCacheStarted -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5940063&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Priority: Major
> Time Spent: 10m
> 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)
