[jira] [Commented] (IGNITE-11406) NullPointerException may occur on client start

2020-12-27 Thread Pavel Vinokurov (Jira)


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

Pavel Vinokurov commented on IGNITE-11406:
--

[~ilyak] Fixed!

> NullPointerException may occur on client start
> --
>
> Key: IGNITE-11406
> URL: https://issues.apache.org/jira/browse/IGNITE-11406
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Assignee: Pavel Vinokurov
>Priority: Critical
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> During testing fixes for https://issues.apache.org/jira/browse/IGNITE-10878
>  # Start cluster, create caches with no persistence and load data into it
>  # Restart each node in cluster by order (coordinator first)
> Do not wait until topology message occurs 
>  # Try to run utilities: activate, baseline (to check that cluster is alive)
>  # Run clients and load data into alive caches
> On 4th step one of the clients throw NPE on start
> {code:java}
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Connection closed, local node received force fail message, will not try to 
> restore connection
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Failed to restore closed connection, will try to reconnect 
> [networkTimeout=5000, joinTimeout=0, failMsg=TcpDiscoveryNodeFailedMessage 
> [failedNodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, order=90, warning=Client 
> node considered as unreachable and will be dropped from cluster, because no 
> metrics update messages received in interval: 
> TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by 
> network problems or long GC pause on client node, try to increase this 
> parameter. [nodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, 
> clientFailureDetectionTimeout=3], super=TcpDiscoveryAbstractMessage 
> [sndNodeId=987d4a03-8233-4130-af5b-c06900bdb6d7, 
> id=3642cfa1961-987d4a03-8233-4130-af5b-c06900bdb6d7, 
> verifierNodeId=d9abbff3-4b4d-4a13-9cb1-0ca4d2436164, topVer=167, 
> pendingIdx=0, failedNodes=null, isClient=false]]]
> 2019-02-23T18:36:24,046][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Discovery notification [node=TcpDiscoveryNode 
> [id=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, addrs=[172.25.1.34], 
> sockAddrs=[lab34.gridgain.local/172.25.1.34:0], discPort=0, order=165, 
> intOrder=0, lastExchangeTime=1550936128313, loc=true, 
> ver=2.4.15#20190222-sha1:36b1d676, isClient=true], 
> type=CLIENT_NODE_DISCONNECTED, topVer=166]
> 2019-02-23T18:36:24,049][INFO 
> ][tcp-client-disco-msg-worker-#4][GridDhtPartitionsExchangeFuture] Finish 
> exchange future [startVer=AffinityTopologyVersion [topVer=165, 
> minorTopVer=0], resVer=null, err=class 
> org.apache.ignite.internal.IgniteClientDisconnectedCheckedException: Client 
> node disconnected: null]
> [2019-02-23T18:36:24,061][ERROR][Thread-2][IgniteKernal] Got exception while 
> starting (will rollback startup routine).
> java.lang.NullPointerException: null
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.internalCacheEx(GridCacheProcessor.java:3886)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.utilityCache(GridCacheProcessor.java:3858)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.updateUtilityCache(GridServiceProcessor.java:290)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart0(GridServiceProcessor.java:233)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart(GridServiceProcessor.java:221)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1038) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1973)
>  [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
>  [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1062)
>  [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:948) 
> [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:847) 
> [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:717) 
> [ignite-core-2.

[jira] [Commented] (IGNITE-11406) NullPointerException may occur on client start

2020-12-25 Thread Ilya Kasnacheev (Jira)


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

Ilya Kasnacheev commented on IGNITE-11406:
--

Can you please rename CacheReadBeforeActivation to 
CacheReadBeforeActivationTest?

> NullPointerException may occur on client start
> --
>
> Key: IGNITE-11406
> URL: https://issues.apache.org/jira/browse/IGNITE-11406
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Assignee: Pavel Vinokurov
>Priority: Critical
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> During testing fixes for https://issues.apache.org/jira/browse/IGNITE-10878
>  # Start cluster, create caches with no persistence and load data into it
>  # Restart each node in cluster by order (coordinator first)
> Do not wait until topology message occurs 
>  # Try to run utilities: activate, baseline (to check that cluster is alive)
>  # Run clients and load data into alive caches
> On 4th step one of the clients throw NPE on start
> {code:java}
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Connection closed, local node received force fail message, will not try to 
> restore connection
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Failed to restore closed connection, will try to reconnect 
> [networkTimeout=5000, joinTimeout=0, failMsg=TcpDiscoveryNodeFailedMessage 
> [failedNodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, order=90, warning=Client 
> node considered as unreachable and will be dropped from cluster, because no 
> metrics update messages received in interval: 
> TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by 
> network problems or long GC pause on client node, try to increase this 
> parameter. [nodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, 
> clientFailureDetectionTimeout=3], super=TcpDiscoveryAbstractMessage 
> [sndNodeId=987d4a03-8233-4130-af5b-c06900bdb6d7, 
> id=3642cfa1961-987d4a03-8233-4130-af5b-c06900bdb6d7, 
> verifierNodeId=d9abbff3-4b4d-4a13-9cb1-0ca4d2436164, topVer=167, 
> pendingIdx=0, failedNodes=null, isClient=false]]]
> 2019-02-23T18:36:24,046][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Discovery notification [node=TcpDiscoveryNode 
> [id=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, addrs=[172.25.1.34], 
> sockAddrs=[lab34.gridgain.local/172.25.1.34:0], discPort=0, order=165, 
> intOrder=0, lastExchangeTime=1550936128313, loc=true, 
> ver=2.4.15#20190222-sha1:36b1d676, isClient=true], 
> type=CLIENT_NODE_DISCONNECTED, topVer=166]
> 2019-02-23T18:36:24,049][INFO 
> ][tcp-client-disco-msg-worker-#4][GridDhtPartitionsExchangeFuture] Finish 
> exchange future [startVer=AffinityTopologyVersion [topVer=165, 
> minorTopVer=0], resVer=null, err=class 
> org.apache.ignite.internal.IgniteClientDisconnectedCheckedException: Client 
> node disconnected: null]
> [2019-02-23T18:36:24,061][ERROR][Thread-2][IgniteKernal] Got exception while 
> starting (will rollback startup routine).
> java.lang.NullPointerException: null
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.internalCacheEx(GridCacheProcessor.java:3886)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.utilityCache(GridCacheProcessor.java:3858)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.updateUtilityCache(GridServiceProcessor.java:290)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart0(GridServiceProcessor.java:233)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart(GridServiceProcessor.java:221)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1038) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1973)
>  [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
>  [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1062)
>  [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:948) 
> [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:847) 
> [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignit

[jira] [Commented] (IGNITE-11406) NullPointerException may occur on client start

2020-12-25 Thread Pavel Vinokurov (Jira)


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

Pavel Vinokurov commented on IGNITE-11406:
--

[~ilyak] Please review

> NullPointerException may occur on client start
> --
>
> Key: IGNITE-11406
> URL: https://issues.apache.org/jira/browse/IGNITE-11406
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Assignee: Pavel Vinokurov
>Priority: Critical
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> During testing fixes for https://issues.apache.org/jira/browse/IGNITE-10878
>  # Start cluster, create caches with no persistence and load data into it
>  # Restart each node in cluster by order (coordinator first)
> Do not wait until topology message occurs 
>  # Try to run utilities: activate, baseline (to check that cluster is alive)
>  # Run clients and load data into alive caches
> On 4th step one of the clients throw NPE on start
> {code:java}
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Connection closed, local node received force fail message, will not try to 
> restore connection
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Failed to restore closed connection, will try to reconnect 
> [networkTimeout=5000, joinTimeout=0, failMsg=TcpDiscoveryNodeFailedMessage 
> [failedNodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, order=90, warning=Client 
> node considered as unreachable and will be dropped from cluster, because no 
> metrics update messages received in interval: 
> TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by 
> network problems or long GC pause on client node, try to increase this 
> parameter. [nodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, 
> clientFailureDetectionTimeout=3], super=TcpDiscoveryAbstractMessage 
> [sndNodeId=987d4a03-8233-4130-af5b-c06900bdb6d7, 
> id=3642cfa1961-987d4a03-8233-4130-af5b-c06900bdb6d7, 
> verifierNodeId=d9abbff3-4b4d-4a13-9cb1-0ca4d2436164, topVer=167, 
> pendingIdx=0, failedNodes=null, isClient=false]]]
> 2019-02-23T18:36:24,046][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Discovery notification [node=TcpDiscoveryNode 
> [id=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, addrs=[172.25.1.34], 
> sockAddrs=[lab34.gridgain.local/172.25.1.34:0], discPort=0, order=165, 
> intOrder=0, lastExchangeTime=1550936128313, loc=true, 
> ver=2.4.15#20190222-sha1:36b1d676, isClient=true], 
> type=CLIENT_NODE_DISCONNECTED, topVer=166]
> 2019-02-23T18:36:24,049][INFO 
> ][tcp-client-disco-msg-worker-#4][GridDhtPartitionsExchangeFuture] Finish 
> exchange future [startVer=AffinityTopologyVersion [topVer=165, 
> minorTopVer=0], resVer=null, err=class 
> org.apache.ignite.internal.IgniteClientDisconnectedCheckedException: Client 
> node disconnected: null]
> [2019-02-23T18:36:24,061][ERROR][Thread-2][IgniteKernal] Got exception while 
> starting (will rollback startup routine).
> java.lang.NullPointerException: null
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.internalCacheEx(GridCacheProcessor.java:3886)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.utilityCache(GridCacheProcessor.java:3858)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.updateUtilityCache(GridServiceProcessor.java:290)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart0(GridServiceProcessor.java:233)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart(GridServiceProcessor.java:221)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1038) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1973)
>  [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
>  [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1062)
>  [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:948) 
> [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:847) 
> [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:717) 
> [ignite-

[jira] [Commented] (IGNITE-11406) NullPointerException may occur on client start

2020-12-25 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11406:


{panel:title=Branch: [pull/8604/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8604/head] Base: [master] : New Tests 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 9{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5803615]]
* {color:#013220}IgniteCacheTestSuite9: 
CacheReadBeforeActivation.readUtilityCacheBeforeActivationFinished - 
PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5803651&buildTypeId=IgniteTests24Java8_RunAll]

> NullPointerException may occur on client start
> --
>
> Key: IGNITE-11406
> URL: https://issues.apache.org/jira/browse/IGNITE-11406
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Assignee: Pavel Vinokurov
>Priority: Critical
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> During testing fixes for https://issues.apache.org/jira/browse/IGNITE-10878
>  # Start cluster, create caches with no persistence and load data into it
>  # Restart each node in cluster by order (coordinator first)
> Do not wait until topology message occurs 
>  # Try to run utilities: activate, baseline (to check that cluster is alive)
>  # Run clients and load data into alive caches
> On 4th step one of the clients throw NPE on start
> {code:java}
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Connection closed, local node received force fail message, will not try to 
> restore connection
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Failed to restore closed connection, will try to reconnect 
> [networkTimeout=5000, joinTimeout=0, failMsg=TcpDiscoveryNodeFailedMessage 
> [failedNodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, order=90, warning=Client 
> node considered as unreachable and will be dropped from cluster, because no 
> metrics update messages received in interval: 
> TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by 
> network problems or long GC pause on client node, try to increase this 
> parameter. [nodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, 
> clientFailureDetectionTimeout=3], super=TcpDiscoveryAbstractMessage 
> [sndNodeId=987d4a03-8233-4130-af5b-c06900bdb6d7, 
> id=3642cfa1961-987d4a03-8233-4130-af5b-c06900bdb6d7, 
> verifierNodeId=d9abbff3-4b4d-4a13-9cb1-0ca4d2436164, topVer=167, 
> pendingIdx=0, failedNodes=null, isClient=false]]]
> 2019-02-23T18:36:24,046][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Discovery notification [node=TcpDiscoveryNode 
> [id=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, addrs=[172.25.1.34], 
> sockAddrs=[lab34.gridgain.local/172.25.1.34:0], discPort=0, order=165, 
> intOrder=0, lastExchangeTime=1550936128313, loc=true, 
> ver=2.4.15#20190222-sha1:36b1d676, isClient=true], 
> type=CLIENT_NODE_DISCONNECTED, topVer=166]
> 2019-02-23T18:36:24,049][INFO 
> ][tcp-client-disco-msg-worker-#4][GridDhtPartitionsExchangeFuture] Finish 
> exchange future [startVer=AffinityTopologyVersion [topVer=165, 
> minorTopVer=0], resVer=null, err=class 
> org.apache.ignite.internal.IgniteClientDisconnectedCheckedException: Client 
> node disconnected: null]
> [2019-02-23T18:36:24,061][ERROR][Thread-2][IgniteKernal] Got exception while 
> starting (will rollback startup routine).
> java.lang.NullPointerException: null
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.internalCacheEx(GridCacheProcessor.java:3886)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.utilityCache(GridCacheProcessor.java:3858)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.updateUtilityCache(GridServiceProcessor.java:290)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart0(GridServiceProcessor.java:233)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart(GridServiceProcessor.java:221)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1038) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1973)
>  [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionE

[jira] [Commented] (IGNITE-11406) NullPointerException may occur on client start

2020-12-23 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-11406:


{panel:title=Branch: [pull/8603/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8603/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5802989&buildTypeId=IgniteTests24Java8_RunAll]

> NullPointerException may occur on client start
> --
>
> Key: IGNITE-11406
> URL: https://issues.apache.org/jira/browse/IGNITE-11406
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Assignee: Pavel Vinokurov
>Priority: Critical
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> During testing fixes for https://issues.apache.org/jira/browse/IGNITE-10878
>  # Start cluster, create caches with no persistence and load data into it
>  # Restart each node in cluster by order (coordinator first)
> Do not wait until topology message occurs 
>  # Try to run utilities: activate, baseline (to check that cluster is alive)
>  # Run clients and load data into alive caches
> On 4th step one of the clients throw NPE on start
> {code:java}
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Connection closed, local node received force fail message, will not try to 
> restore connection
> 2019-02-23T18:36:24,045][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Failed to restore closed connection, will try to reconnect 
> [networkTimeout=5000, joinTimeout=0, failMsg=TcpDiscoveryNodeFailedMessage 
> [failedNodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, order=90, warning=Client 
> node considered as unreachable and will be dropped from cluster, because no 
> metrics update messages received in interval: 
> TcpDiscoverySpi.clientFailureDetectionTimeout() ms. It may be caused by 
> network problems or long GC pause on client node, try to increase this 
> parameter. [nodeId=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, 
> clientFailureDetectionTimeout=3], super=TcpDiscoveryAbstractMessage 
> [sndNodeId=987d4a03-8233-4130-af5b-c06900bdb6d7, 
> id=3642cfa1961-987d4a03-8233-4130-af5b-c06900bdb6d7, 
> verifierNodeId=d9abbff3-4b4d-4a13-9cb1-0ca4d2436164, topVer=167, 
> pendingIdx=0, failedNodes=null, isClient=false]]]
> 2019-02-23T18:36:24,046][DEBUG][tcp-client-disco-msg-worker-#4][TcpDiscoverySpi]
>  Discovery notification [node=TcpDiscoveryNode 
> [id=80f8b6ee-6a6d-4235-86e9-1b66ea310eb6, addrs=[172.25.1.34], 
> sockAddrs=[lab34.gridgain.local/172.25.1.34:0], discPort=0, order=165, 
> intOrder=0, lastExchangeTime=1550936128313, loc=true, 
> ver=2.4.15#20190222-sha1:36b1d676, isClient=true], 
> type=CLIENT_NODE_DISCONNECTED, topVer=166]
> 2019-02-23T18:36:24,049][INFO 
> ][tcp-client-disco-msg-worker-#4][GridDhtPartitionsExchangeFuture] Finish 
> exchange future [startVer=AffinityTopologyVersion [topVer=165, 
> minorTopVer=0], resVer=null, err=class 
> org.apache.ignite.internal.IgniteClientDisconnectedCheckedException: Client 
> node disconnected: null]
> [2019-02-23T18:36:24,061][ERROR][Thread-2][IgniteKernal] Got exception while 
> starting (will rollback startup routine).
> java.lang.NullPointerException: null
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.internalCacheEx(GridCacheProcessor.java:3886)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.utilityCache(GridCacheProcessor.java:3858)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.updateUtilityCache(GridServiceProcessor.java:290)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart0(GridServiceProcessor.java:233)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onKernalStart(GridServiceProcessor.java:221)
>  ~[ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1038) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1973)
>  [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1716)
>  [ignite-core-2.4.15.jar:2.4.15]
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1144) 
> [ignite-core-2.4.15.jar:2.4.15]
> at 
> org.apache.ignite.internal.IgnitionEx.startC