Show the gook as this is the marshalled rmi stub that the NamingContext is trying to use, and it contains the address/port the is causing the connection failure. SANDBOX:1099 is only the bootstrap port used to obtain the rmi stub. The rmi address should be the same as the --host value.
-- xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
Rod Macpherson wrote:
When running multihome I am getting this on all of the office machines but not on my home network: same version of JBoss, same JDK, same application works fine at home.
[NamingContext] Failed to connect to SANDBOX:1099
Ironically this used to work on this very machine. When not specifying --host it everything works fine so there is something twisted about the multihome on our network. I can telnet in to SANDBOX port 1099 and I get back a bunch of gobbledygook that looks like a sane JNDI service connection so it is listenting. I am beginning to think this is a security feature issue on Windows XP that was added but who knows.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
