[
https://issues.apache.org/jira/browse/IGNITE-8776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533253#comment-16533253
]
kcheng.mvp commented on IGNITE-8776:
------------------------------------
[~slukyanov]
Thank you very much!
The fix pretty much done, but I have an unclear and I posted in the forum. Can
you have a check ?
http://apache-ignite-developers.2346864.n4.nabble.com/Why-GridCacheEvictionManager-always-use-cfg-getEvictionPolicy-cfg-getEvictionPolicyFactory-even-ther-td32230.html
> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> ----------------------------------------------------------------------------
>
> Key: IGNITE-8776
> URL: https://issues.apache.org/jira/browse/IGNITE-8776
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Stanislav Lukyanov
> Assignee: kcheng.mvp
> Priority: Minor
> Labels: newbie
>
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered
> if evictionPolicyFactory is set instead of evictionPolicy (the latter is
> deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find
> either an *MBean interface or IgniteMBeanAware interface on the passed
> object. It works for LruEvictionPolicy but not for LruEvictionPolicyFactory
> (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered
> (IgniteKernalMbeansTest does that for kernal mbeans - need the same for cache
> beans).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
