;
> Instead, is it possible to write a template using some kind of regexp and
> ignoring classloader id ? To avoid issues with multiple templates I suggest
> always output classloaderId in hierarchy.
>
>
> вс, 13 июн. 2021 г. в 16:01, Igor Akkuratov :
>
> > Stanislav, t
hat in mind, I'd rather have a new option like
> IGNITE_MBEAN_STATIC_HIERARCHY
> - IGNITE_MBEAN_STATIC_HIERARCHY=true (default): the new behavior is in
> effect, IGNITE_MBEAN_APPEND_CLASS_LOADER_ID is ignored
> - IGNITE_MBEAN_STATIC_HIERARCHY=false: the old behavior is in
Alexei, thank you for your response.
> 1. I don't understand why setting
> IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false + igniteInstanceName is not a
> solution to your issue ?
> Just put it in the documentation and this should do fine.
It could be a solution for me, but I believe that such approach
Is there anybody alive?
Hello, everyone!
Because there was no cons, I have started developing and I have pull request
https://github.com/apache/ignite/pull/8972 now.
Review it please.
> Sent: Friday, December 18, 2020 at 4:58 PM
> From: "¿ ¿"
> To: dev@ignite.apache.org
> Subject: Static hierarchy in jmx t
Igor Akkuratov created IGNITE-12920:
---
Summary: Static hierarchy in jmx tree
Key: IGNITE-12920
URL: https://issues.apache.org/jira/browse/IGNITE-12920
Project: Ignite
Issue Type
Igor Akkuratov created IGNITE-12889:
---
Summary: checkRingLatency loops if there is only one server node
with client in topology
Key: IGNITE-12889
URL: https://issues.apache.org/jira/browse/IGNITE-12889
Igor Akkuratov created IGNITE-11091:
---
Summary: Visor shows all indexes in upper case
Key: IGNITE-11091
URL: https://issues.apache.org/jira/browse/IGNITE-11091
Project: Ignite
Issue Type
