Brian Stansberry wrote:
Galder Zamarreno wrote:
> I'm about to fix https://jira.jboss.org/jira/browse/JBCACHE-1465
> make sure we don't encounter Thread name issues when using Cache
> instances in LOCAL mode but I wanted to raise the following:
> In clustered mode, cluster name allows for each cache instance to be
> distinguished individually but when it comes to LOCAL mode, there's
> not a cache name as such, so if you had N LOCAL caches in a server,
> how would you differentiate from one another when trying to search for
> that instance in your JMX console?
> I think we could do with a cache name in general rather than limiting
> us to a cluster name which by extension is used as the cache name in a
> replicated environment.
I don't think the "generate name" logic even applies after 1.x. Unless
I've forgotten something, in 2.0+ a user has to specify the ObjectName.
Yep, I'd forgotten something; the whole
o.j.c.jmx.PlatformMBeanServerRegistration business. So this still applies.
Lead, AS Clustering
JBoss, a division of Red Hat