Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 497F718498 for ; Thu, 10 Dec 2015 07:10:11 +0000 (UTC) Received: (qmail 62312 invoked by uid 500); 10 Dec 2015 07:10:11 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 62244 invoked by uid 500); 10 Dec 2015 07:10:11 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 62222 invoked by uid 99); 10 Dec 2015 07:10:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2015 07:10:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 018E82C1F5A for ; Thu, 10 Dec 2015 07:10:11 +0000 (UTC) Date: Thu, 10 Dec 2015 07:10:11 +0000 (UTC) From: "Semen Boikov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (IGNITE-1684) NPE in GridCacheProcessor.processClientReconnectData on client left MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-1684. ---------------------------------- Resolution: Fixed > 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: Artem Shutak > 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)