> The JMX Connectors are not written for JBoss specific. Because JMX allows > you > to have more than one MBeanServer per JVM and there is a good chance that > a box have more than one JVM running this is not so far fetched. Especially > when > an external JNDI server is used.
Ok, that is fine, but how can we work with the connector as is so that we can have easy access to it. Our admin clients are using the connector to gain remote access to the MBeanServer. Currently this is limited to deployer.sh, but I will eventually be changing shutdown to use it (so that it is not dependent on the html adapter) and I will be writting a command line console which will also use it. So the problem is finding the connector for a single machine and still allow a failr generic scheme to bind other connectors into. How about something like this: jmx/local/rmi jmx/somehost/rmi jmx/someotherhost/rmi Where jmx/local/rmi is always the connector for the vm which the JNDI service is running in. Then the others are bound with the dns name of the host which the connector is for. Use : for / if you like, : will still allow for tree-like nesting right? just JNDIView doesn't know about them? This way we are both happy. I can get to the connector for the server I am talking too by specifing Context.PROVIDER_URL without needing to know wthat the hostname of that vm is as the vm sees it. Sound reasonable? --jason _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
