[
https://issues.apache.org/jira/browse/IGNITE-16416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17483931#comment-17483931
]
Ignite TC Bot commented on IGNITE-16416:
----------------------------------------
{panel:title=Branch: [pull/9775/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9775/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6388652&buildTypeId=IgniteTests24Java8_RunAll]
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 class path 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)
