[
https://issues.apache.org/jira/browse/IGNITE-16416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-16416:
--------------------------------------
Summary: Unreadable result on cluster deactivation via IgniteMXBean (was:
Bad result serialization on cluster deactivation in IgniteMXBean)
> Unreadable result on cluster deactivation via IgniteMXBean
> ----------------------------------------------------------
>
> Key: IGNITE-16416
> URL: https://issues.apache.org/jira/browse/IGNITE-16416
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.12
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Minor
> Attachments: Scr_Bad.png, Scr_Good.png
>
>
> IgniteMXBean can throw IgniteException on the cluster deactivation. It's is
> OK with the exception itself - cluster must not be deactivated without
> 'force' flag if that would issue data loss. Unfortunately, I'd forgotten that
> such exception is bound to the classpass and might not be serialized by other
> remote size like jconsole.
> See 'bad' picture. Same refuse on the deactivation, bad the error is
> unreadable.
> See 'good' picture. Some readable result.
> Solution: let's convert the exception to a 'java-core' one.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
