Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1455808756070-3085.post@n6.nabble.com>
References: <1455745424588-3064.post@n6.nabble.com>
	<1455753201492-3066.post@n6.nabble.com>
	<CAKZNQ8FsJPe3HURvz_pgqz17DXzRuPk=qTOLM7Bf=LCHdvecGw@mail.gmail.com>
	<CAGt6o8mH4G=gT=Zaz27mGGOEZoC3xDKr=4hK+A7OP5v=8BFKCw@mail.gmail.com>
	<1455808756070-3085.post@n6.nabble.com>
Date: Fri, 19 Feb 2016 13:34:25 +0300
Message-ID: 
 <CAGt6o8=H5xibOCiCurCkPtOKurtNpAmU8gKC5j-_YSUhhxu1qg@mail.gmail.com>
Subject: Re: changed cache configuration and restarted server nodes. Getting
 exception.
From: Vladimir Ozerov <vozerov@gridgain.com>
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a113fb4d4f3c5f0052c1d06fa

--001a113fb4d4f3c5f0052c1d06fa
Content-Type: text/plain; charset=UTF-8

Hi Vinay,

It looks like we have several problems here.

First, Visor clear task doesn't work. Most probably this relates to Ignite
internal components serialization problem which is currently being fixed as
a part of IGNITE-2649 ticket.

Second - the main problem:

org.apache.ignite.binary.BinaryObjectException: Cannot find metadata
for object with compact footer: -135842108


It looks like something is wrong with binary serialization of your objects.
Please add the following XML snippet to your XML configuration and restart
nodes. It should help:

<property name="binaryConfiguration">
    <bean class="org.apache.ignite.configuration.BinaryConfiguration">
        <property name="compactFooter" value="false"/>
    </bean>
</property>

Though, this is not the solution, but rather a workaround. In order to
understand the root cause we need exact steps to reproduce the problem. Is
it possible to provide the source code of the key and value classes you put
into cache?

Vladimir.

On Thu, Feb 18, 2016 at 6:19 PM, vinshar <vinsharma.tech@gmail.com> wrote:

> Hi Vladimir,
>
> Please find attached stack traces and visor output for my multiple tries to
> identify and resolve issue. Also find attached my server side
> configurations. We start all caches from client in local mode and all
> distributed caches have to be defined in server configs. Cache in attached
> file with entries (name ends with _ALL) is local cache. Other caches are
> replicated and defined in server configs.
>
> Attached stack trace file contains topology and cache statistics during
> these multiple tries. I tried cleaning caches on a node by its ID and also
> clearing a cache by its name but both failed. attached file has stack
> traces
> for all.
> I have masked some information like IPs etc. let me know in case if you
> need
> any more information.
>
> default-config.xml
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/n3085/default-config.xml
> >
>
> visor_ignite_stack_trace_masked.txt
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/n3085/visor_ignite_stack_trace_masked.txt
> >
>
> Regards,
> Vinay Sharma
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3085.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

--001a113fb4d4f3c5f0052c1d06fa
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Vinay,<div><br></div><div>It looks like we have several=
 problems here.=C2=A0</div><div><br></div><div>First, Visor clear task does=
n&#39;t work. Most probably this relates to Ignite internal components seri=
alization problem which is currently being fixed as a part of IGNITE-2649 t=
icket.</div><div><br></div><div>Second - the main problem:</div><div><pre s=
tyle=3D"word-wrap:break-word;white-space:pre-wrap"><font color=3D"#990000">=
org.apache.ignite.binary.BinaryObjectException: Cannot find metadata for ob=
ject with compact footer: -135842108</font></pre></div><div><br></div><div>=
It looks like something is wrong with binary serialization of your objects.=
 Please add the following XML snippet to your XML configuration and restart=
 nodes. It should help:</div><div><font face=3D"monospace, monospace" color=
=3D"#990000"><br></font></div><div><div><font face=3D"monospace, monospace"=
 color=3D"#990000">&lt;property name=3D&quot;binaryConfiguration&quot;&gt;<=
/font></div><div><font face=3D"monospace, monospace" color=3D"#990000">=C2=
=A0 =C2=A0 &lt;bean class=3D&quot;org.apache.ignite.configuration.BinaryCon=
figuration&quot;&gt;</font></div><div><font face=3D"monospace, monospace" c=
olor=3D"#990000">=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;property name=3D&quot;comp=
actFooter&quot; value=3D&quot;false&quot;/&gt;</font></div><div><font face=
=3D"monospace, monospace" color=3D"#990000">=C2=A0 =C2=A0 &lt;/bean&gt;</fo=
nt></div><div><font face=3D"monospace, monospace" color=3D"#990000">&lt;/pr=
operty&gt;</font></div></div><div><br></div><div>Though, this is not the so=
lution, but rather a workaround. In order to understand the root cause we n=
eed exact steps to reproduce the problem. Is it possible to provide the sou=
rce code of the key and value classes you put into cache?</div><div><br></d=
iv><div>Vladimir.</div></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Thu, Feb 18, 2016 at 6:19 PM, vinshar <span dir=3D"ltr">&lt;=
<a href=3D"mailto:vinsharma.tech@gmail.com" target=3D"_blank">vinsharma.tec=
h@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Vlad=
imir,<br>
<br>
Please find attached stack traces and visor output for my multiple tries to=
<br>
identify and resolve issue. Also find attached my server side<br>
configurations. We start all caches from client in local mode and all<br>
distributed caches have to be defined in server configs. Cache in attached<=
br>
file with entries (name ends with _ALL) is local cache. Other caches are<br=
>
replicated and defined in server configs.<br>
<br>
Attached stack trace file contains topology and cache statistics during<br>
these multiple tries. I tried cleaning caches on a node by its ID and also<=
br>
clearing a cache by its name but both failed. attached file has stack trace=
s<br>
for all.<br>
I have masked some information like IPs etc. let me know in case if you nee=
d<br>
any more information.<br>
<br>
default-config.xml<br>
&lt;<a href=3D"http://apache-ignite-users.70518.x6.nabble.com/file/n3085/de=
fault-config.xml" rel=3D"noreferrer" target=3D"_blank">http://apache-ignite=
-users.70518.x6.nabble.com/file/n3085/default-config.xml</a>&gt;<br>
<br>
visor_ignite_stack_trace_masked.txt<br>
&lt;<a href=3D"http://apache-ignite-users.70518.x6.nabble.com/file/n3085/vi=
sor_ignite_stack_trace_masked.txt" rel=3D"noreferrer" target=3D"_blank">htt=
p://apache-ignite-users.70518.x6.nabble.com/file/n3085/visor_ignite_stack_t=
race_masked.txt</a>&gt;<br>
<br>
Regards,<br>
Vinay Sharma<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://apache-ignite-users.70518.x=
6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting=
-exception-tp3064p3085.html" rel=3D"noreferrer" target=3D"_blank">http://ap=
ache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-resta=
rted-server-nodes-Getting-exception-tp3064p3085.html</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">Sent from the Apache Ignite Users m=
ailing list archive at Nabble.com.<br>
</div></div></blockquote></div><br></div>

--001a113fb4d4f3c5f0052c1d06fa--