dcsimg
RMI callback problem -- (invalid IP)
0 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Jason_Hallstrom
Posted On:   Friday, February 1, 2002 12:21 PM

I have an old peer-to-peer RMI application that was working fine until I upgraded my Red Hat machine to JDK 1.3.1_02-b02. To the best of my knowledge nothing else has changed. I have three nodes on an internal network. Machine 1: 192.168.1.3, Windows 2000, JRE 1.3.1_01a Machine 2: 192.168.1.5, Windows NT 4.0, JRE 1.3.1_01a Machine 3: 192.168.1.1, Red Hat 7.2, JRE 1.3.1_02-b02, (rmiregistry runs here) The application is fairly straightforward. A client object connects to a server object(via Naming.Lookup()), and the server object invokes a method on the client. If I run the client software from Machine 2, everything works fine.    More>>

I have an old peer-to-peer RMI application that was working fine until I upgraded my Red Hat machine to JDK 1.3.1_02-b02. To the best of my knowledge nothing else has changed.



I have three nodes on an internal network.



Machine 1: 192.168.1.3, Windows 2000, JRE 1.3.1_01a



Machine 2: 192.168.1.5, Windows NT 4.0, JRE 1.3.1_01a



Machine 3: 192.168.1.1, Red Hat 7.2, JRE 1.3.1_02-b02, (rmiregistry runs here)



The application is fairly straightforward. A client object connects to a server object(via Naming.Lookup()), and the server object invokes a method on the client.



If I run the client software from Machine 2, everything works fine.



If I run the client software from Machine 1, a connection is established to the remote object on Machine 3 without a problem. When Machine 3 attempts to perform the callback, I receive the following error: java.rmi.ConnectionException: connection refused to host: 192.168.0.1



The thing that is driving me crazy is that the client is coming from 192.168.1.1, not 192.168.0.1!



192.168.0.1 does not even exist on my network.



I'm not sure how to debug such a low-level problem. Any help would be greatly appreciated.

   <<Less
About | Sitemap | Contact