[
https://issues.apache.org/jira/browse/IGNITE-13753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238830#comment-17238830
]
Alexey Goncharuk commented on IGNITE-13753:
-------------------------------------------
[~agura] [~nizhikov] can you take a look at the changes? The tests are failing
in master as well (.NET inspections are related to TC update and Cache5 fails
with some random errors - I will try to investigate and file a separate
ticket(s)).
> 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
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{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)
