From issues-return-76984-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Sat Sep 29 13:34:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5BB36180672 for ; Sat, 29 Sep 2018 13:34:05 +0200 (CEST) Received: (qmail 82282 invoked by uid 500); 29 Sep 2018 11:34:04 -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 82273 invoked by uid 99); 29 Sep 2018 11:34:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Sep 2018 11:34:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DAD32180AE3 for ; Sat, 29 Sep 2018 11:34:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id gMQ-fQugIQb1 for ; Sat, 29 Sep 2018 11:34:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2A23B5F4A1 for ; Sat, 29 Sep 2018 11:34:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A71C7E0E87 for ; Sat, 29 Sep 2018 11:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 22DA92775D for ; Sat, 29 Sep 2018 11:34:00 +0000 (UTC) Date: Sat, 29 Sep 2018 11:34:00 +0000 (UTC) From: "Igor Kamyshnikov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-8788) Getting NullPointerException during commit into cassandra, after reconnecting to ignite server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-8788?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D166= 32961#comment-16632961 ]=20 Igor Kamyshnikov commented on IGNITE-8788: ------------------------------------------ There is one other aspect of this issue. Let's assume that ignite server config has Cassandra caches A and B. And ig= nite client config has A, B and C. If such ignite client joins the cluster = it infects it: no other clients would be able to join this cluster even if = they have just A and B caches defined in their configs (their Ignition.star= t threads will hang). New Ignite server nodes would not be able to join the= cluster as well (dying with the exception mentioned in the ticket). And ev= en if that "bad" client leaves the cluster, the cluster cannot be joined by= new correct clients and servers. =C2=A0 =C2=A0 > Getting NullPointerException during commit into cassandra, after reconnec= ting to ignite server > -------------------------------------------------------------------------= --------------------- > > Key: IGNITE-8788 > URL: https://issues.apache.org/jira/browse/IGNITE-8788 > Project: Ignite > Issue Type: Bug > Components: cassandra > Reporter: Yashasvi Kotamraju > Assignee: Igor Rudyak > Priority: Major > > When ignite client reconnects to restarted ignite server, while commiting= data into cassandra=C2=A0NullPointerException=C2=A0 is observed for random= runs. > caused by: java.lang.NullPointerException=C2=A0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 at=C2=A0 > org.apache.ignite.cache.store.cassandra.persistence.PojoField.getValueFro= mObject(PojoField.java:167)=C2=A0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 at=C2=A0 > org.apache.ignite.cache.store.cassandra.persistence.PersistenceController= .bindValues(PersistenceController.java:450)=C2=A0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 at=C2=A0 > org.apache.ignite.cache.store.cassandra.persistence.PersistenceController= .bindKeyValue(PersistenceController.java:202)=C2=A0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 at=C2=A0 > org.apache.ignite.cache.store.cassandra.session.transaction.WriteMutation= .bindStatement(WriteMutation.java:58)=C2=A0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0 at=C2=A0 > org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.exec= ute(CassandraSessionImpl.java:499)=C2=A0 > =C2=A0 > After going through the source code=C2=A0 > there is a suspicion that its a java serialization issue in ignite cassan= dra=C2=A0 > module=C2=A0 > In org.apache.ignite.cache.store.cassandra.persistence.PojoField.java, th= ere=C2=A0 > is a PojoFieldAccessor instance variable which is transient type, so it w= ill=C2=A0 > not be part of serialization and if PojoField object is serialized and th= en=C2=A0 > deserialized it would have PojoFieldAccessor as null. And in the Exceptio= n=C2=A0 > we are seeing the same, NullPointerException when getValue(..) is called = on=C2=A0 > null PojoFieldAccessor in PojoField.getValueFromObject() method . So when= =C2=A0 > ever PojoField object is serialized and then deserialized we might be=C2= =A0 > observing the issue.=C2=A0 > Reproducer can be found at: > http://apache-ignite-users.70518.x6.nabble.com/Getting-NullPointerExcepti= on-during-commit-into-cassandra-after-reconnecting-to-ignite-server-td22005= .html > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)