Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DD37B191D6 for ; Fri, 8 Apr 2016 10:47:41 +0000 (UTC) Received: (qmail 43707 invoked by uid 500); 8 Apr 2016 10:47:41 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 43660 invoked by uid 500); 8 Apr 2016 10:47:41 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 43651 invoked by uid 99); 8 Apr 2016 10:47:41 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Apr 2016 10:47:41 +0000 Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 62A711A00E2 for ; Fri, 8 Apr 2016 10:47:41 +0000 (UTC) Received: by mail-lf0-f52.google.com with SMTP id j11so76215255lfb.1 for ; Fri, 08 Apr 2016 03:47:41 -0700 (PDT) X-Gm-Message-State: AD7BkJL0E5/3v2pqdij2a1wYjw/yYgiGTOQoezrbNJ6NMwd9sgBns3d8vncDMkYujZ5WaUcgvglgsa1AeUKGL5SV MIME-Version: 1.0 X-Received: by 10.25.139.194 with SMTP id n185mr2847078lfd.79.1460112459795; Fri, 08 Apr 2016 03:47:39 -0700 (PDT) Received: by 10.114.98.133 with HTTP; Fri, 8 Apr 2016 03:47:39 -0700 (PDT) In-Reply-To: <1460109664781-4021.post@n6.nabble.com> References: <1459439892329-3819.post@n6.nabble.com> <1459901452035-3944.post@n6.nabble.com> <1460051353311-4001.post@n6.nabble.com> <1460073131015-4009.post@n6.nabble.com> <1460082253727-4013.post@n6.nabble.com> <1460087588985-4016.post@n6.nabble.com> <1460109664781-4021.post@n6.nabble.com> Date: Fri, 8 Apr 2016 13:47:39 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Behavior of init() for clustered singleton From: Yakov Zhdanov To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a113ebf647fad79052ff6ec63 --001a113ebf647fad79052ff6ec63 Content-Type: text/plain; charset=UTF-8 Guys, It seems there can be a race condition between service methods call and initialization - org/apache/ignite/internal/processors/service/GridServiceProcessor.java:921 Alex G, Val, can you please check if service may be called prior to its initialization? Dan, can you please add service instance identity hash code to output in init() and other service methods. Smth like - System.out.println("Inside service XXX method [thread=" + Thread.currentThread().getName() + ", hash=" + System.identityHashCode(this) + ']'); --Yakov 2016-04-08 13:01 GMT+03:00 dstieglitz : > If you look at the line below: > > > https://github.com/dstieglitz/grails-ignite/blob/v0.4.x/src/java/org/grails/ignite/IgniteCronDistributedRunnableScheduledFuture.java#L79 > > We're seeing the string "NULL EXECUTOR" in our status. But based on the way > the classes are initialized I don't think it's possible for that reference > to be null. Also we've observed the scheduler working, so at this point I > think our main issue was confusion caused by this seemingly null reference. > > I'm not sure exactly what is not serialized, all we see is this null > evaluation return true. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Behavior-of-init-for-clustered-singleton-tp3819p4021.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > --001a113ebf647fad79052ff6ec63 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Guys,

It seems there can be a race cond= ition between service methods call and initialization -=C2=A0org/apache/ign= ite/internal/processors/service/GridServiceProcessor.java:921
Alex G, Val, can you please check if service may be called prio= r to its initialization?

Dan, can you please add s= ervice instance identity hash code to output in init() and other service me= thods. Smth like -=C2=A0System.out.println("Inside service = XXX method [thread=3D" + Thread.currentThread= ().getN= ame() + ", hash=3D" + System.identityHashCode(this= = ) + ']');

--Yakov

2016-04-08 13:01 GMT+03:00 dstieglitz <dstieglitz@stainlesscode.com>:
If you look at the line below:

https://github.com/dstieglitz/grails-ig= nite/blob/v0.4.x/src/java/org/grails/ignite/IgniteCronDistributedRunnableSc= heduledFuture.java#L79

We're seeing the string "NULL EXECUTOR" in our status. But ba= sed on the way
the classes are initialized I don't think it's possible for that re= ference
to be null. Also we've observed the scheduler working, so at this point= I
think our main issue was confusion caused by this seemingly null reference.=

I'm not sure exactly what is not serialized, all we see is this null evaluation return true.



--
View this message in context: http://apache-ignite-users.70518.x6.nabbl= e.com/Behavior-of-init-for-clustered-singleton-tp3819p4021.html
Sent from the Apache Ignite Users m= ailing list archive at Nabble.com.

--001a113ebf647fad79052ff6ec63--