[
https://issues.jboss.org/browse/ISPN-3531?page=com.atlassian.jira.plugin....
]
Tomas Sykora commented on ISPN-3531:
------------------------------------
At very first sight it looks like it should really impact only MassIndexer stuff... it
means only 1 particular operation which is callable using JON UI and Infinispan Library
plugin.
Names in plugin etc. are generated automatically according to MBean names and managed
operations, so once it renames, plugin should be ok with that.
It can only affects my testing but I hope in a positive way. From failing to passing
(after very small modification) :)
I will thoroughly dive into it probably tomorrow, Thursday (if we are in a hurry, let me
know, I will prioritize it)
LifecycleManager of query module inadvertently unregisters MBeans
belonging to other cache managers
---------------------------------------------------------------------------------------------------
Key: ISPN-3531
URL:
https://issues.jboss.org/browse/ISPN-3531
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 6.0.0.Alpha4
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Labels: 620
Fix For: 6.0.0.Final
The ObjectName used for query related MBeans does not contain the name of the cache
manager as an attribute to ensure disambiguation. Thus, if two cache managers are
configured to share the same JMX domain their query related MBean names would clash and
shutting down one of the managers would also unregister the MBeans belonging to the
other(s).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira