[
https://jira.jboss.org/jira/browse/ISPN-223?page=com.atlassian.jira.plugi...
]
Galder Zamarreno commented on ISPN-223:
---------------------------------------
Actually, the address is different even if you have two CMs start in the same machine.
This is thanks to JGroups' logical addresses :)
So, the only faq to write about is in case you start two CMs in the same machine and both
are configured to be local, since the address in that case is simply 'local'
(getAddress() would return null in normal circumstances, but it makes sense to use a more
meaningful word for jmx)
CacheManager needs to identifiable
----------------------------------
Key: ISPN-223
URL:
https://jira.jboss.org/jira/browse/ISPN-223
Project: Infinispan
Issue Type: Feature Request
Components: JMX, reporting and management
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.0.0.CR1
We need CacheManager's to expose some kind of name or id that differenciates them
from the rest.
The jmxDomain is not enough since you could have different machines running different VMs
deploying the CacheManager instances with the same jmxDomain and this is valid.
The reason we need this is so that Jopr can show different cache manager's amongst
their resources. Currently, it can only show one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira