I had been setting the properties through the JNLP, and then through the lib/jnpi.properties file for the command line test. I removed those, and tried a command line test using the example code you gave. The first time was a timeout, after I forgot to change the server name (oops) but after fixing that, the result was another connection refused from 127.0.0.1. This happened with both the HTTPS and JNP interfaces.
What I think is happening is that it's looking up the EJB, and the server is telling it to get it from 127.0.0.1, rather than from the server's local network address.... ... playing with it while replying ... BINGO. :-D While digging around looking for answers, I found that the server was in fact resolving itself to the external (nat'd www) IP address. This meant that the address used for this stuff couldn't get past the firewall. I noticed this while shutting down the server, it said the name wasn't bound. So as far as JBoss was concerned, it couldn't access 210.x.x.x, and it never knew about 192.168.0.10, so sending 127.0.0.1 was a perfectly resonably thing to do :-/ I'd actually fixed this yesterday while the server was up, but it didn't re-bind, so the fix didn't really get fixed until I restarted JBoss. Oops. Thanks for the help folks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3832026#3832026 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3832026 ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
