Dmitry,
You can to try execute build() for the specific object:
BinaryObject operation = ignite.binary()
.builder("SomeObject")
.setField("FIELD", value)
.build();
(or something similar for java object)
after the client reconnected. In my mind, the class descriptor should be
loaded to system cache (if it not exist).
On Fri, Dec 16, 2016 at 10:49 AM, dmitry.parkhonin <dmitry.parkho...@db.com>
wrote:
> Hi val (valery? :)),
>
> Thanks for reply.
>
> Yes, switching off compact footer helped me in this case.
> But the whole issue seems strange - my client stops working after a single
> node cluster is restarted. To make the whole system working I have to
> restart all my clients.
> Is this the behavior that is expected?
>
> Regards,
> Dmitry.
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/BinaryObjectException-after-
> Ignite-restarts-tp9552p9588.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Vladislav Pyatkov
