We have encountered a problem at one of our clients where we have our java client running on a windows machine and jboss running on an AIX.
The network setup at the client is as follows:
- java client running on network 'A' with jdk1.4.2
- jboss 3.2.3 on AIX running on network 'B' with jdk1.4.2. The AIX machine has 3 network addresses of which only one address is public.
We passed in the -b 10.247.25.189 (public address of the AIX) to the run.sh to make jboss bind to the public address and can see it used through the logs on the server.log:
[org.jboss.naming.NamingService] Started jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/10.247.25.189, etc.....
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.20.12; nested exception is: java.net.ConnectException: Connection refused: connect] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:647) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347)
props.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); props.put("java.naming.provider.url", "10.247.25.189:1099"); props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
For those interested, I think I have found a solution to my problem.
There was a fix in jboss 3.2.5, http://sourceforge.net/docman/display_doc.php?docid=23676&group_id=22866, that mentions setting the bind address to the generated RMI stubs.
This sounds alot like it addresses my problem