You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "David Harvey (JIRA)" <ji...@apache.org> on 2018/10/03 14:24:00 UTC
[jira] [Updated] (IGNITE-7616) GridDataStreamExecutor and
GridCallbackExecutor JMX beans return incorrect values due to invalid
interface registration.
[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Harvey updated IGNITE-7616:
---------------------------------
Attachment: image-2018-10-03-10-23-24-676.png
> GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-7616
> URL: https://issues.apache.org/jira/browse/IGNITE-7616
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Max Shonichev
> Assignee: David Harvey
> Priority: Major
> Labels: jmx
> Fix For: 2.7
>
> Attachments: image-2018-10-03-10-23-24-676.png, master_1b3742f4d7_mxbeans_threads2.patch
>
>
> Two of newly added management beans as a result of implementing feature request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs:
> # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean interface, though actually it is an incompatible StripedExecutor.
> # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean interface, though actually it is an incompatible IgniteStripedThreadPoolExecutor.
> # ThreadPoolMXBeanAdapter checks whether adapted instance is ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as -1 or null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)