If you get an error like this when you try to connect to the JBoss server:
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 10.10.34.77; nested exception is:
java.net.ConnectException: Connection timed out: connect]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:707)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
and the address (in this case 10.10.34.77) listed is no longer in use it is because the server remembers its startup address and hands it back to the client on the initial port (usually 1099). Unfortunately it is difficult to distinguish this connect error from one where the server is genuinely un-reachable.
This occurs on our development machines and stand-alone laptop deployments when someone starts up the server while wireless networking is connected and then disconnects wireless on the server machine. The client sucessfully finds the server using the jndi.properties url, but then the server hands back an old, stale address on the wireless subnet.
