This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am having a problem setting up RMI using WebSphere 188.8.131.52 on AIX. When I start the JVM, rebinding succeeds. However, when I go into the application and make an RMI call, here is the error message I am seeing:
[12/8/06 16:11:10:498 UTC] 3e141124 SystemErr R java.rmi.ConnectException: Connection refused to host: 184.108.40.206; nested exception is: java.net.ConnectException: Connection refused [12/8/06 16:11:10:499 UTC] 3e141124 SystemErr R at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:585)
The two servers are 158.8 and 158.9
rmiregistry is running on port 1099 on both, when I netstat -an I see port 1099 listening on both. rmiregistry was started before the JVM came up. Also if I telnet to 220.127.116.11 1099 from 158.8, it works, and vice versa.
Going crazy here. Any ideas? [ December 08, 2006: Message edited by: Chad Naber ]
Joined: Mar 25, 2005
So I determined what the problem is here, and I thought I would post the solution for everyone's reference:
There is a problem with AIX machines that have 2 NICs and IBM WebSphere. If you have 2 IPs on the AIX machine, WebSphere uses the first IP in the hosts file for rmiregistry regardless of the rmi deployment descriptors.
The fix is to use these parameters when starting rmiregistry: