[jbosscache-issues] [JBoss JIRA] Commented: (JBCACHE-1465) Make MBean name independent of Thread name when used in LOCAL mode.

[Galder Zamarreno (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBCACHE-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448508#action_12448508 ] 

Galder Zamarreno commented on JBCACHE-1465:
-------------------------------------------

Another alternative is to use a java.rmi.server.UID which "represents an identifier that 
is unique over time with respect to the host it is generated on, or one of 2<sup>16</sup> 
"well-known" identifiers."

> Make MBean name independent of Thread name when used in LOCAL mode.
> -------------------------------------------------------------------
>
>                 Key: JBCACHE-1465
>                 URL: https://jira.jboss.org/jira/browse/JBCACHE-1465
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.1.GA
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 3.0.2.GA
>
>
> When using JBossCache in LOCAL mode, make it's MBean independent of the thread name to avoid
> potential issues with specific thread names.
> Alternatives include using UUID.randomUUID().toString() as part of the MBean name but as the instance
> will only be LOCAL, we only need to make sure the MBean name is unique in the VM, so Manik's 
> suggestion to use Integer.toHexString(System.identityHashCode(objectToRegister)) in JBCACHE-1444
> should be enough.
> We also have to take account that UUIDs are not very readable.

-- 
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