[
https://issues.apache.org/jira/browse/IGNITE-12890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083279#comment-17083279
]
Maria Makedonskaya commented on IGNITE-12890:
---------------------------------------------
[PDS
(Indexing)|https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsIndexing?branch=pull%2F7667%2Fhead]
 suite timeout is not related to my changes.
> JMX attribute 'getExecutorServiceFormatted' of IgniteMXBean returns
> getPublicThreadPoolSize() instead of formatted executor service
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-12890
> URL: https://issues.apache.org/jira/browse/IGNITE-12890
> Project: Ignite
> Issue Type: Bug
> Reporter: Maria Makedonskaya
> Assignee: Maria Makedonskaya
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> while testing JmxWorker I found a possible bug in one of attributes of
> IgniteMXBean
> 1. start ignite node with IGNITE_JMX_PORT=1100
> 2. get ExecutorServiceFormatted attribute via JMX
> {noformat}
> /usr/lib/jvm/java-8-oracle/bin/java -cp
> ./ignite-test-tools-1.0.0-SNAPSHOT.jar org.apache.ignite.testtools.JmxWorker
> -host=127.0.0.1 -port=1100 -bean=IgniteKernal -group=Kernal
> -attribute=ExecutorServiceFormatted
> 8
> {noformat}
> a number does not looks like proper value for string representation of
> complex object, browsing the code reveals following:
> {noformat}
> @Override public String getExecutorServiceFormatted() {
> assert cfg != null;
> return String.valueOf(cfg.getPublicThreadPoolSize());
> }
> {noformat}
> We should deprecate 'getExecutorServiceFormatted' and create a new method
> 'getPublicThreadPoolSize'.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
