7 Replies Latest reply on Jan 25, 2006 4:29 PM by Dimitris Andreadis

    Consistency in JMX naming

    Greg Hinkle Newbie

      I'd like to reopen the question of why hashcodes are being added to jndi names should local-jndi-name not be set (http://jira.jboss.com/jira/browse/JBAS-275). This issue creates a big problem for building mangement services. We can not require all customers to set a local-jndi-name, nor should we have to as this is due to an implementation detail.

      I've seen it mentioned that the hashcode is used intstead of the archive name because a jar could be deployed in two ears. In that case use ear/jar/name. I see the case for use refs for JNDI lookup, but I can't agree with not having a stable ObjectName. Other servers vary the domain, or utilize a separate (stable) key property.

      Just wanted to see what others thought about the importance of stable jmx object names. I saw Scott mention in a post that he thought the jsr77 name should break out the id into a separate keyproperty (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=60696) but that doesn't seem to have been done.