[
https://jira.jboss.org/jira/browse/ISPN-267?page=com.atlassian.jira.plugi...
]
Galder Zamarreno commented on ISPN-267:
---------------------------------------
Using InetAddress.getLocalHost().getHostName should be fine because the jmx code in the vm
always tries to bind to InetAddress.anyLocalAddress(), which is 0.0.0.0. So, there's
no way you can start two jmx agents in the same port in a machine, hence, for only naming
purposes, we can safely assume that there won't be 2 identical combos of
InetAddress.getLocalHost().getHostName():<jmx:port>
Change Infinispan cache manager jmx name to be
hostname:<jmx-port> based
------------------------------------------------------------------------
Key: ISPN-267
URL:
https://jira.jboss.org/jira/browse/ISPN-267
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 4.0.0.CR1
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.0.0.CR2
<galderz> until now, i had named the CacheManager in jopr as:
global-jmx-domain@address
<galderz> this is a bit of pain because the address changes everytime you restart
infinispan
<galderz> but jopr does not realise this and considers an infinispan started in
same jmx port in same address to be the same
<galderz> so, when you restart, u see infinispan cache manager in jopr but it has
the wrong name, this will be confusing
<galderz> heiko told me this is a limitation of the jopr
<galderz> on top of that, if u wanna do things correctly and import the new cache
manager, u need to delete the old one, let auto discovery run and get the new one
<galderz> and then you're back to your starting point, so if had tweaked any
scheduling options in the previous infinispan instance, you're back to defaults
<galderz> so, i'm gonna change this name to simply be:
global-jmx-domain@InetAddress.getLocalHost().getHostName():<jmx:port>
<galderz> that way we'll avoid this confusion and you can always get the
address from the RpcManager, so not big deal
--
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