JBoss versus Sun JMX implementation

[rtompot]

I have a concern, probably due to my relative inexperience with Java in general, about consistency in JMX-implementation classes used within JBoss and by JMX-enabled remote applications.

My scenario is that I have a servlet deployed in JBoss that looks up JMXConnectorServers registered in JNDI of remote apps and effectively connects to these remote MBeanServers using the JSR-160 API.

So, if JBoss as well as these remote apps are all running in JVMs launched by the Tiger (1.5) JRE, are the Sun JMX implementation classes effectively loaded and used by all parties? Or is there a possibility that there will be problems by a mixing in of the JBoss JMX implementation? (The remote apps have jbossall-client.jar within their classpath)

[starksm64]

It works for me. Unless there is a problem what is the concern about how the jmx implementations interact?

[rtompot]

Yes, it works for me too. What I am looking to further understand what is happening vis-a-vis the different JMX implementations so as to have the confidence that as I add in additional functionality using the JMX API (e.g., remote notifications, JMX agent services, etc.), there will not be problems cropping up because I have not fully understood what is happening behind the scenes.

My analysis of the boot class paths for JBoss and my remote apps indicate that all will be using Sun's JMX implementation (in rt.jar), so it appears to me that JBoss is using Sun's implementation rather than it's own implementation? I guess basically I am looking for confirmation/denial of this conclusion...

Thanks...

[starksm64]

The server uses both implementations. See org.jboss.system.server.jmx.LazyMBeanServer. Only the javax.* classes from the jdk are used regardless.