You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (Jira)" <ji...@apache.org> on 2020/11/24 15:17:00 UTC
[jira] [Assigned] (IGNITE-13753) Non-thread-safe collection is used
for the list of registered MBeans in JmxMetricExporterSpi
[ https://issues.apache.org/jira/browse/IGNITE-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk reassigned IGNITE-13753:
-----------------------------------------
Assignee: Alexey Goncharuk
> Non-thread-safe collection is used for the list of registered MBeans in JmxMetricExporterSpi
> --------------------------------------------------------------------------------------------
>
> Key: IGNITE-13753
> URL: https://issues.apache.org/jira/browse/IGNITE-13753
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Priority: Major
>
> {{MetricManager}} registry creation and remove listeners can be invoked concurrently (the only synchronization is via {{map.computeIfAbsent}} which provides key-level granularity.
> As a result, some of the beans are lost and I get an occasional assertion on
> {code}
> boolean rmv = mBeans.remove(mbeanName);
> assert rmv;
> {code}
> Changing the collection to a synchronized list should suffice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)