Mailing-List: contact users-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@apex.apache.org
Date: Fri, 11 Aug 2017 17:13:55 -0700 (MST)
From: Vivek Bhide <vivek.bhide@target.com>
To: users@apex.incubator.apache.org
Message-ID: <1502496835555-1840.post@n6.nabble.com>
In-Reply-To: <CAA7LveHuH46uPX_42aQz1=3O=ckS3CyQq-nqq2HQLo8=P-ZbQg@mail.gmail.com>
References: <CAA7LveEsG2jM9vhvZ9fzHidCGWQG3uvLiO7EALd+YSLUjW9DmQ@mail.gmail.com> <CA+5xAo3QOvA2fdk31sBmc2k8nc=-0x7vD+d_OfL0M4r=9eudBA@mail.gmail.com> <CAA7LveEWH02bLPqVCsGhLmyW8zJ4Gw5+sKzFg7Fz-_6AWXh=8g@mail.gmail.com> <CAA7LveHXTGVPxgkoPkaPJJBOnWWa85AeyQQbTiufW=SvROHgdQ@mail.gmail.com> <1502431519677-1834.post@n6.nabble.com> <CAA7LveHf+Mb6OwaLF+y93SsRngAdqUYbRCtH34=m=YMf9pu3Zg@mail.gmail.com> <1502473149788-1836.post@n6.nabble.com> <CAA7LveEh_TfMgPpv0oucMr3CikiafSArKA1i_QvDk4UYSC7tYQ@mail.gmail.com> <1502475187029-1838.post@n6.nabble.com> <CAA7LveHuH46uPX_42aQz1=3O=ckS3CyQq-nqq2HQLo8=P-ZbQg@mail.gmail.com>
Subject: Re: How the application recovery works when its started with
 -originalAppId
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Sat, 12 Aug 2017 00:14:05 -0000

Hi Pramod and Thomas

Below are my findings till now on this issue

1. Fix suggested by Pramod and fix made as apart of
https://issues.apache.org/jira/browse/APEXMALHAR-2526 are doing the same
thing
2. In the comments for https://issues.apache.org/jira/browse/APEXMALHAR-2526
I found that, the new class KryoJavaSerializer.java is created to fix the
problem but kryo has already fixed this issue at their end too (in Dec 2016)
3. When checked the kryo version from apex-core, I found that it is
expecting version 2.24 which is quite old and latest kryo version (4.0.1)
has the fix included
4. So at the end only changes I needed were to update kryo version to latest
and continue using a JavaSerializer. On implementing these, Issue with
application recovery has resolved

I see that story https://issues.apache.org/jira/browse/APEXCORE-768 is
already created to update the kryo version and remove class
KryoJavaSerializer.java

Again this still doesn't answer the question that why kryo is not
serializing the custom implementation of LinkedHashMap at first place with
its default serialization

Regards
Vivek


--
View this message in context: http://apache-apex-users-list.78494.x6.nabble.com/How-the-application-recovery-works-when-its-started-with-originalAppId-tp1821p1840.html
Sent from the Apache Apex Users list mailing list archive at Nabble.com.