[
https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575631#comment-16575631
]
David Harvey edited comment on IGNITE-7616 at 8/10/18 1:09 AM:
---------------------------------------------------------------
I have a solution coded and running against 2.5.
The main issue is I needed to have IgniteStripedThreadPoolExecutor use
Executors.newFixedThreadPool(1, factory) rather than
newSingleThreadExecutor(factory) because the latter hides the underlying
ThreadPoolExecutor. That hiding may have value in cases where the
ThreadPoolExecutor is exposed, but IgniteStripedThreadPoolExecutor is providing
another level of delegation anyway.
was (Author: syssoftsol):
I have a solution coded and running against 2.5.
The main issue is I needed to have IgniteStripedThreadPoolExecutor use
Executors.newFixedThreadPool(1, factory) rather than
newSingleThreadExecutor(factory) because the latter hides the underlying
ThreadPoolExecutor. That hiding may have value in cases where the
ThreadPoolExecutor is exposed, but IgniteStripedThreadPoolExecutor is providing
another level of delegation anyway.
> 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
>
>
> 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)