On Sun, 12 May 2002, Jason Dillon wrote: > Currently we are binding to "jmx:<hostname>:rmi" which is fine when you are > working with the localhost, but will start to cause problems once used in a > multi-host environment. > ... > > So for a client on a remote host to correctly make use of the deployer.sh or any > other simialr tool using the jmx adapter it will have to have knowledge of the > servers local hostname (as returned by > java.net.InetAddress.getLocalHost().getHostName()) and specify that value for > --server, then specify -Djava.naming.provider.url=jnp://www.mydomain.com.
This may also be an issue if you have a client running in the same host as the server, but on a VM from other vendor. When I run java.net.InetAddress.getLocalHost().getHostName() on a Sun VM, I get something like "myhost.mydomain.com". When I do the same thing on an IBM VM for Linux, I get "myhost". This appears to be the reason the whole testsuite fails if I use a Sun VM for the server and an IBM VM for the testsuite clients (or vice-versa). Regards, Francisco _______________________________________________________________ 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
