Re: Unmarshalable result from the MX beans

2022-02-04 Thread Maksim Timonin
Hi Vladimir, I think that var 3. is OK. Currently `clusterStates` javadocs declares `IgniteCheckedException` but actually throws `IgniteException`. So this is a bug in any case, so I think we can just replace it with JMException. I'd like to propose to use the same approach for other JMX methods

Unmarshalable result from the MX beans

2022-02-03 Thread Vladimir Steshin
    Hi, Igniters.     We've found that invocation results from some MX beans might not be properly represented on clients like jconsole [1]. In the exception cases. We pass Ignite exceptions or JMException with Ignite exception causes to the client. And the client fails to unmarshal unknown e