ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Shutak (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-1684) NPE in GridCacheProcessor.processClientReconnectData on client left
Date Wed, 14 Oct 2015 15:16:05 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Artem Shutak updated IGNITE-1684:
---------------------------------
    Description: 
I've got NPE on server node in next scenario:
- 4 servers and 2 clients (on one physical machine)
- one server node has been killed
- 1 client "Failed to reconnect" and leave {{[22:24:52,382][ERROR][tcp-client-disco-reconnector-#9%null][TcpDiscoverySpi]
Failed to reconnect}}
- At the same time (see timing) got NPE (see below)
- started one new servers, which couldn't connect to cluster (may be after NPE)

See "trans-write-invoke" logs.
{noformat}
[22:24:53,079][ERROR][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Runtime error caught
during grid runnable execution: IgniteSpiThread [name=tcp-disco-msg-worker-#2%null]
java.lang.NullPointerException
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.processClientReconnectData(GridCacheProcessor.java:2011)
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1904)
	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
	at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3310)
	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3002)
	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2095)
	at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5382)
	at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{noformat}

In additional, after it (left 3 server node + 1 client)
- one more server has been killed
- the last client said  "Failed to reconnect"
- and another server node got the same NPE

  was:
I've got NPE on server node in next scenario:
- 4 servers and 2 clients (on one physical machine)
- one server node has been killed
- 1 client "Failed to reconnect" and leave {{[22:24:52,382][ERROR][tcp-client-disco-reconnector-#9%null][TcpDiscoverySpi]
Failed to reconnect}}
- At the same time (see timing) got NPE (see below)
- started one new servers, which couldn't connect to cluster (may be after NPE)

See "trans-write-invoke" logs.
{noformat}
[22:24:53,079][ERROR][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Runtime error caught
during grid runnable execution: IgniteSpiThread [name=tcp-disco-msg-worker-#2%null]
java.lang.NullPointerException
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.processClientReconnectData(GridCacheProcessor.java:2011)
	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1904)
	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
	at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3310)
	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3002)
	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2095)
	at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5382)
	at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{noformat}


> NPE in GridCacheProcessor.processClientReconnectData on client left
> -------------------------------------------------------------------
>
>                 Key: IGNITE-1684
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1684
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Artem Shutak
>            Assignee: Semen Boikov
>             Fix For: 1.5
>
>
> I've got NPE on server node in next scenario:
> - 4 servers and 2 clients (on one physical machine)
> - one server node has been killed
> - 1 client "Failed to reconnect" and leave {{[22:24:52,382][ERROR][tcp-client-disco-reconnector-#9%null][TcpDiscoverySpi]
Failed to reconnect}}
> - At the same time (see timing) got NPE (see below)
> - started one new servers, which couldn't connect to cluster (may be after NPE)
> See "trans-write-invoke" logs.
> {noformat}
> [22:24:53,079][ERROR][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Runtime error caught
during grid runnable execution: IgniteSpiThread [name=tcp-disco-msg-worker-#2%null]
> java.lang.NullPointerException
> 	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.processClientReconnectData(GridCacheProcessor.java:2011)
> 	at org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDiscoveryDataReceived(GridCacheProcessor.java:1904)
> 	at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.onExchange(GridDiscoveryManager.java:659)
> 	at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1706)
> 	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3310)
> 	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3002)
> 	at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2095)
> 	at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5382)
> 	at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {noformat}
> In additional, after it (left 3 server node + 1 client)
> - one more server has been killed
> - the last client said  "Failed to reconnect"
> - and another server node got the same NPE



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message