I don’t know how fix deserialization, it seems very internal. But I can do
something for exception handling, but only on weekend.
Andrey.
От: Denis Magda
Отправлено: 26 сентября 2019 г. в 0:30
Кому: user@ignite.apache.org
Копия: Ilya Kasnacheev
Тема: Re: Exception during exception handling
r that cause transaction fail should
> not be lost anyway. It seems “try finaly” block should be implemented
> inside “catch” section. Because we have chance to get exception during
> exception handling anyway.
>
>
>
> Andrey.
>
>
>
> *От: *Denis Magda
> *Отправлено: *25 се
, it is unsafe exception handling,
information about origin error that cause transaction fail should not be lost
anyway. It seems “try finaly” block should be implemented inside “catch”
section. Because we have chance to get exception during exception handling
anyway.
Andrey.
От: Denis Magda
Отправлено
Hello Andrey and thanks for reporting!
This reminds me of this issue that has a similar stack trace:
https://issues.apache.org/jira/browse/IGNITE-12178
Ilya, looks like the root cause is absolutely the same, doesn't it?
-
Denis
On Wed, Sep 25, 2019 at 10:02 AM Andrey Davydov
wrote:
> In
In ignite 2.7.5 I got following exception:
org.apache.ignite.IgniteException: Failed to create string representation of
binary object.
at
org.apache.ignite.internal.util.tostring.GridToStringBuilder.toStringImpl(GridToStringBuilder.java:1022)
~[ignite-core-2.7.5.jar:2.7.5]
at
