RMI Callback Connection Refused Problem

we are running Red Hat Linux 9, we previously had a problem connecting a server and client running in 2 different PC's. we had the following error
Exception in mainjava.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused
we used the -Djava.rmi.server.hostname= <hostname> option to make it run. Now, were trying to make use of call backs this time we ran into another problem having the error:
Exception in mainjava.rmi.ConnectException: Connection refused to host: 172.16.100.24; nested exception is:
java.net.ConnectException: Connection refused
what are we doing wrong?

We already included a security manager. but the error is still there.

Similar Messages

Connection refused problem..., please help.

I am running the server on PC (Windows 98) and I got
this message:
java.rmi.ConnectionException: Connection refused to host: 33186; nested exception is:
java.net.ConnectException: Connection refused: no further information
I got both server and client policy. So this is the way I run the server:
java -Djava.security.policy=server.policy CalcServer
where CalcServer is the name of the server.
anybody can help please post.
Thanks,
Ted.

sorry, I forgot to run rmiregistry.
Problem solved.

Java.rmi.ConnectException: Connection refuse

Hi all,
I have built a simple RMI client server application.I can run client & server fine locally.
However if I test this appplication over the internet, I get this exception on the client:
java.rmi.ConnectException: Connection refused to host: 169.254.157.53; nested exception is:
java.net.ConnectException: Connection timed out: connectConnection refused to host:169.254.157.53
The RMI server is running on my PC and the client on a friend's remote PC.Both PCs are connected to Internet.
I don't have any firewall running on my PC (including windows XP firewall). The server RMI lookup on the client happens correctly,
the exception is raised when the client tries to call the remote method on the server.
Here is an extract of my RMI server code (it works locally):
public static void main(String[] args) throws Exception {
          try {
          // args[0] contains the database server name given as command line argument, arg[1] contains binary path that contains weather jpeg files
          CPrimaryWeatherServer test = new CPrimaryWeatherServer(args[0], args[1]);
          Naming.rebind("rmi://localhost:1099/WeatherPrimaryService", test);
          System.out.println("Serveur m�t�o principal d�marr�");
          } catch (Exception e){ System.out.println(e.getMessage());}
Here is an extract of my RMI client code (it works locally):
try{
                    rec=1;
                    leftClik=1;
                    System.out.println("Before RMI lookup");
                    IPrimaryWeatherServerService serveur =(IPrimaryWeatherServerService)Naming.lookup("rmi://"+primWS+":1099/WeatherPrimaryService");
                    System.out.println("After RMI lookup");
                    System.out.println("Before server method call");
                    z=serveur.getFullWeatherData(); --> exception is raised here
                    System.out.println("After RMI server method call");
I am directly connected to Internet using an ethernet card connected to an ADSL modem.169.254.157.53 is the automatic IP of my network card different from the IP given by my ISP. By the way, the client tries to contact me using my DNS name that resolves correctly to my ISP IP adress.
Thanks a lot for help,

because I am guessing that a local IP address is being embedded into the stub so the clien't can't find the remote server. I am guessing because you didn't provide the exception or its text. Anyway the suggestion will cause the correct public IP address/hostname to be embedded into the stub.

Java.rmi.ConnectionExceptionException:Connect refused to host

I write a rmi,when server and client runs in the same machine,it runs ok,then I run them in two machines,server runs in 192.168.0.1,like follows:
C:\>rmiregistry -J-Djava.security.policy=registerit.policy
C:\>java -Djava.rmi.dgc.leaseValue=1000 -Djava.security.policy=registery.policy RegisterIt
Object instantiated: HelloServer[RemoteStub [ref: [endpoint:[192.168.0.1:3120](l
ocal),objID:[0]]]]
and it ok ,client runs in 192.168.0.2, but it raise errors:
java -Djava.security.policy=registerit.policy HelloClient
HelloClient exception :java.rmi.ConnectionException:Connection refused to host:192.168.0.2;nested exception is:java.net.ConnectException:Connection refused:connect
Why? how to solve it?
Any idea will be appreciated!
My code is follows:
HelloInterface.java
public interface HelloInterface extends java.rmi.Remote{
public String sayHello() throws java.rmi.RemoteException;
HelloServer.java
import java.io.*;
import java.rmi.*;
import java.rmi.server.*;
import java.util.*;
public class HelloServer extends UnicastRemoteObject implements HelloInterface{
public HelloServer() throws RemoteException{
super();
public String sayHello() throws RemoteException{
return "Hello world, the current system time is "+new Date();
RegisterIt.java
import java.rmi.*;
public class RegisterIt{
public static void main(String args[]){
try{
HelloServer obj=new HelloServer();
System.out.println("Object instantiated: "+obj);
Naming.rebind("/HelloServer",obj);
System.out.println("HelloServer bound in registery");
catch(Exception e){
System.out.println(e);
registerit.policy
grant{
permission java.security.AllPermission;
HelloClient.java
import java.rmi.*;
public class HelloClient{
public static void main(String args[]){
if(System.getSecurityManager()==null){
System.out.println("null");
System.setSecurityManager(new RMISecurityManager());
try{
HelloInterface obj=(HelloInterface)Naming.lookup("/HelloServer");
String message=obj.sayHello();
System.out.println(message);
catch(Exception e){
System.out.println("HelloClient exception: "+e);
}

Connection refused means the server is no listening on the port that client tried to connect to. You need to look at your configuration.

Invocation time Exception (java.rmi.ConnectException: Connection refused to

Hi folks,
SERVER = LINUX
CLIENT = WINDOWS 200
JAVA VERSION : 1.4.2
Object obj = Naming.lookup("rmi://x.x.x.x:5578/MyServer");
System.out.println("Object ="+obj); // Works fine and return stub as shown in o/p
MyServer_Stub server = (MyServer_Stub)obj;
server.validate(); // throws following Connection refused exception
-----OUTPUT-----
Object =com.MyServer_Stub[RemoteStub [ref: [endpoint:[x.x.x.x:42360](remote),objID:[a981ca:10722cb9411:-8000, 0]]]]
java.rmi.ConnectException: Connection refused to host: x.x.x.x.x; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)[
     at com.MyServer_Stub.validate(Unknown Source)/b]
     at tescasees.testbyexample.rmi.MyServerChangesTestApplication.main
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:452)
     at java.net.Socket.connect(Socket.java:402)
     at java.net.Socket.<init>(Socket.java:309)
     at java.net.Socket.<init>(Socket.java:124)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
     ... 5 more
Exception in thread "main"
[b] Why does java system throws exception at invoke time not connection time at lookup time</b]
Any suggestion...
Regards,
Manoj

> Are you getting this from a lookup()? If so it means the Registry you are looking for at rmi://x.x.x.x:5578 is not present.
I am getting it at the time when I invoke the method validate on the object returned from lookup.
--Manoj

Java.rmi.ConnectException: Connection refused to host: 10.41.8.140; nested exception is:

Agile:9.2.2.1
linux-x86_64

What is the Port in which you are ruinning the RMI?
You need to mention the port.
Simply chek if you have proper connectivity to the Server and the RMI Service as the speicifed port, try the debugging commands from command prompt like:
D:>telnet <Server IP Address> <Port Number>
If this command clears the windows into a blank window as if waiting for you input then it means that you have access to the Server and the RMI service is running on the machine.
If not, it is either NOT accessible or RMI Service is not working.
Thanks and regards,
Pazhanikanthan. P

What does java.rmi.ConnectException: Connection refused to host mean? ¶

Several users have run into a java.rmi.ConnectException message during deployment, and need some information on how to troubleshoot this. We'll be adding this to our documentation, but thought it might be useful now.
In NoSQL DB R2.0, the show plan -id <id> command displays plan status and any errors that may have occurred. If you see this exception listed in the error section, it means that the Admin service was unable to reach one of the NoSQL DB components while the system was trying to execute an administrative command.
The first step is check on the overall status of the store. One way to do that is to use the show topology command, followed by the verify command. The show topology command will display the layout of the store, while verify will check the status of each component. A component that can't be reached will display a status of UNREACHABLE.
In general, NoSQL DB attempts to make any troubleshooting information you need available through the Admin CLI, through commands like show plan, show events, show faults. A ConnectException message means that a communication channel either was not established, or failed, and in those cases, troubleshooting information may not have been conveyed to the Admin service. This is particularly true if there was a communication failure during initial deployment of a component.
The next step would be to look in the NoSQL log files for more detailed error information. Look first in the aggregated storewide log, which can be found in the node that is hosting the master admin service, under the KVROOT/<storename>/logs/<storename>*.log. You can locate the master Admin through the "verify" command. This log file contains information from all the different components in the store.
Suppose Replication Node rg1-rn3, on Storage Node sn3, is not responsive. Look through the <storename>.log for entries made by those components. Each log entry is prefixed with the name of the component that issued the log message. Sometimes the aggregated storewide log has too much information, or sometimes information from a component was not transmitted to the Admin, and therefore isn't included in the aggregated log. In that case, it can be more helpful to look at the Replication Node or Storage Node logs directly, which can be found on their host, in the <KVROOT>/<storename>/logs directory.
If the problem occurs during an initial deployment, it can be particularly helpful to review the Storage Node logs to make sure that the Storage Node Agent on that node was created correctly, and that the process came up as expected, according to the installation directions, and the Replication Node logs. Some of the common reasons why a Replication Node might not come up are that here is inadequate heap and memory on the node, or that a initial configuration parameter is misspelled or has an invalid value, or that the time skew between components is greater than NoSQL's acceptable limit.

Several users have run into a java.rmi.ConnectException message during deployment, and need some information on how to troubleshoot this. We'll be adding this to our documentation, but thought it might be useful now.
In NoSQL DB R2.0, the show plan -id <id> command displays plan status and any errors that may have occurred. If you see this exception listed in the error section, it means that the Admin service was unable to reach one of the NoSQL DB components while the system was trying to execute an administrative command.
The first step is check on the overall status of the store. One way to do that is to use the show topology command, followed by the verify command. The show topology command will display the layout of the store, while verify will check the status of each component. A component that can't be reached will display a status of UNREACHABLE.
In general, NoSQL DB attempts to make any troubleshooting information you need available through the Admin CLI, through commands like show plan, show events, show faults. A ConnectException message means that a communication channel either was not established, or failed, and in those cases, troubleshooting information may not have been conveyed to the Admin service. This is particularly true if there was a communication failure during initial deployment of a component.
The next step would be to look in the NoSQL log files for more detailed error information. Look first in the aggregated storewide log, which can be found in the node that is hosting the master admin service, under the KVROOT/<storename>/logs/<storename>*.log. You can locate the master Admin through the "verify" command. This log file contains information from all the different components in the store.
Suppose Replication Node rg1-rn3, on Storage Node sn3, is not responsive. Look through the <storename>.log for entries made by those components. Each log entry is prefixed with the name of the component that issued the log message. Sometimes the aggregated storewide log has too much information, or sometimes information from a component was not transmitted to the Admin, and therefore isn't included in the aggregated log. In that case, it can be more helpful to look at the Replication Node or Storage Node logs directly, which can be found on their host, in the <KVROOT>/<storename>/logs directory.
If the problem occurs during an initial deployment, it can be particularly helpful to review the Storage Node logs to make sure that the Storage Node Agent on that node was created correctly, and that the process came up as expected, according to the installation directions, and the Replication Node logs. Some of the common reasons why a Replication Node might not come up are that here is inadequate heap and memory on the node, or that a initial configuration parameter is misspelled or has an invalid value, or that the time skew between components is greater than NoSQL's acceptable limit.

Rmi client throws Connection Refused exception

My Rmi client throws a Connection Refused exception when i try to run it on remote machine (in this case i run it on my virtualbox macine).
The virtualbox machine network is in NAT mode (host machine ip should be 10.0.2.2).
When rmi client starts get registry instance and print in standar output:
RegistryImpl_Stub[UnicastRef2 [liveRef: [endpoint:[//10.0.2.2/:1099,util,RmiInstances$1@1275d39](remote),objId:[0:0:0, 0]]]]But when rmi client trys to use any of remote methods it throws Connection Refused, but it's to strange because the Connection Refused has 127.0.1.1 as ip.
java.rmi.ConnectException: Connection refused to host: 127.0.1.1; ....In client RmiInstances code (this class contains all remote implementations) is:
public class RmiInstances {
    private static RmiInstances instance;
    private IUserManage userManage;
    private IAnalysis analysis;
    private IPacientManage pacientManage;
    private IInsuranceManage insuranceManage;
    private Config config;
    private RmiInstances()
            throws RemoteException, NotBoundException, IOException {
        this.config = Config.getInstance();
        Registry registry = LocateRegistry.getRegistry(config.getServerUrl()+"/",
                1099, new RMIClientSocketFactory() {
            @Override
            public Socket createSocket(String host, int port) throws IOException {
                try {
                    URI uri = new URI(config.getServerUrl()+
                            ":"+config.getServerPort());
                    return new Socket(uri.getHost(), uri.getPort());
                } catch (URISyntaxException ex) {
                    ex.printStackTrace();
                    return null;
        System.out.println(registry);
        userManage = (IUserManage)registry.lookup("RUserManage");
        analysis = (IAnalysis)registry.lookup("RAnalysis");
        pacientManage = (IPacientManage)registry.lookup("RPacientManage");
        insuranceManage = (IInsuranceManage)registry.lookup("RInsuranceManage");
...And server code is the next:
public static void main(String[] args) {
     System.out.println("GNULab Server " + VERSION + " starting...");
     System.setProperty("java.rmi.server.codebase",
          "file:/home/zarovich/workspace/labserver/bin");
     try {
         // Loading config
         System.out.println("Loading config...");
         Config config = Config.getInstance();
         // inicializando rmi registry
         Registry registry;
         if (config.isSsl()) {
          registry = LocateRegistry.createRegistry(
               config.getServerPort(), new RmiSSLClient(),
               new RmiSSLServer());
         } else
          registry = LocateRegistry
               .createRegistry(config.getServerPort());
         // instanciando implementaciones
         RAnalysis rAnalysis = new RAnalysis();
         RInsuranceManage rInsuranceManage = new RInsuranceManage();
         RPacientManage rPacientManage = new RPacientManage();
         RUserManage rUserManage = new RUserManage();
         // registrando interfaz rmi
         registry.rebind("RAnalysis", (IAnalysis) UnicastRemoteObject.exportObject(rAnalysis, 0));
         registry.rebind("RInsuranceManage", (IInsuranceManage) UnicastRemoteObject.exportObject(rInsuranceManage, 0));
         registry.rebind("RPacientManage", (IPacientManage) UnicastRemoteObject.exportObject(rPacientManage, 0));
         registry.rebind("RUserManage", (IUserManage) UnicastRemoteObject.exportObject(rUserManage, 0));
         System.out.println("GNULab Server " + VERSION + " listening ...");
         System.out.println("Registry instance: " + registry.toString());
     } catch (RemoteException e) {
         e.printStackTrace();
        * catch (MalformedURLException e) { e.printStackTrace(); }
        */catch (IOException e) {
         // TODO Auto-generated catch block
         e.printStackTrace();
     } catch (JDOMException e) {
         // TODO Auto-generated catch block
         e.printStackTrace();
...

I'm solved my problem.
I just need run my server with -Djava.rmi.serverhost=10.0.2.2 and my client running on my virtualbox machine works!

Connection refused in RMI

Hi everybody,
I am trying to run a java application in a distributed environment using linux m/cs.I tested the application using a single machine successfully but whenever i am trying to run my application among several machines then things are going wrong.I am facing a problem regarding java RMI.
The commands i have given are:
rmiregistry -J-Djava.security.policy=.java.policy & {.java.policy is my policy file}
java -Djava.security.policy=.java.policy [arguments]
i disabled the firewall and placed all the class definitions in the local classpath in all machines.
i placed the policy file(.java.policy) in usere's directory.
It looks like:
grant {
permission java.security.AllPermission;
permission java.net.SocketPermission "*", "accept, connect, listen, resolve";
The problem is Whenever i am trying to lookup the remote object from a remote machine,most of the time it fails giving following error.
java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
.............With some more error..............
one thin more I didn't use localhost address(127.0.0.1) as the argument anywhere in the code and i am not getting the reason why the error is coming involving 127.0.0.1. . I only used real network ddresses like(192.168.9.45, or...)in the program and according to the code it should try to connect to some real network address but it is giving error involving 127.0.0.1.
So what should i do? Even i have tried with a very simple code to fetch the remote object in a test application under the same environment but it is giving the same error.
Pls help.

OK, just found this myself after several hours of frustration...
Check your /etc/hosts file on the server, and remove any line linking the loopback ip address (127.0.0.1) to localhost (or anything else).
Your machine should I think have a static IP address for that to work properly elsewhere in the system.
After that, restart the RMI server and try again.
That did it for me.

RMI: connection refused error while invoking remote method from client mac.

Hi All,
when i run client program, which is calling remote object from other system, it shows the below error.
please help me solving this issue, i also have policy file and installed security manager.
Exception in Cliendjava.rmi.ConnectException: Connection refused to host: 10.66.
112.137; nested exception is:
java.net.ConnectException: Connection refused: connect
thanks in advance.
Regards,
Anand.

See item A.1 of the [RMI FAQ|http://java.sun.com/j2se/1.5.0/docs/guide/rmi/faq.html].

RMI connection refused

Hello to all,
I have created and completed an RMI chat application and tested it on my localhost. It worked all right.
Now I want to make it live i.e. run it through internet.
Is it same as running on localhost only we have to change the IP address for locating registry.
I have done that and uploaded the server file on host, also I have the IP address of that host.
I have replaces localhost whit the give IP address but connection refused exception is thrown.
I have located the registry on the server through IP address then when I use
Registry reg=LocateRegistry("xx.xx.xx.xxx");
System.out.println("1");
chatAppIF chatStub=(chatAppIF)Naming.lookup("rmi://xx.xx.xx.xxx:xxxx/service");
System.out.println("2");
int i=chatStub.logMeIn(user,pass);
System.out.println("3");Output screen shows
1
2
Client exception: java.rmi.ConnectException: Connection refused to host: xx.xx.xx.xxx; nested exception is:
java.net.ConnectException: Connection refused: connectWhile when i use
Registry reg=LocateRegistry("xx.xx.xx.xxx");
System.out.println("1");
chatAppIF stub=(chatAppIF)reg.lookup("service");
System.out.println("2");
int i=chatStub.logMeIn(user,pass);
System.out.println("3");it give output as
1
Client exception: java.rmi.ConnectException: Connection refused to host: xx.xx.xx.xxx; nested exception is:
java.net.ConnectException: Connection refused: connectIs there is difference between naming.lookup() and reg.lookup() method?
I think Naming.lookup() finds the registry but cannot find the method logMeIn() while reg.lookup() has no success.
anyway why the connection is refused?

The argument to Naming.bind()/rebind()/unbind() and Naming.lookup() is a URI of the form rmi://hostname[:port]/path.
The argument to Registry.bind()/rebind()/unbind() and Registry.lookup() is just the path part.
The data returned by Naming.list() is an array of URIs.
The data returned by Registry.list() is an array of paths.
In other words Naming.list() returns items which can be used as arguments to Naming.lookup(), and Registry.list() returns items which can be used as arguments to Registry.lookup().
The reason is that when you construct a Registry, via LocateRegistry.getRegistry(), you supply the host and port at that point, so specifying it again in the bind/lookup string would be redundant. There's nothing stopping you doing that but the resulting name won't be compatible with what Naming.bind() would have done.

RMI newbie connection problem

One machine (WindowsXP). Hello world test app. RMIRegistry is running. I start my server and get
HelloImp1 err: Connection refused to host: ron; nested exception is:
     java.net.ConnectException: Connection refused: connect
java.rmi.ConnectException: Connection refused to host: ron; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:313)
     at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source)
     at java.rmi.Naming.rebind(Naming.java:160)
     at rmitest.ServerImpl.main(ServerImpl.java:30)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:426)
     at java.net.Socket.connect(Socket.java:376)
     at java.net.Socket.<init>(Socket.java:291)
     at java.net.Socket.<init>(Socket.java:119)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
     ... 6 more
Process terminated with exit code 0
My policy file (which it is read because it gacks on syntax errors) is
grant {
     permission java.security.AllPermission;
import rmitest.Server;
import java.rmi.*;
import java.rmi.server.UnicastRemoteObject;
public class ServerImpl extends UnicastRemoteObject implements Server
     private String name;
     public ServerImpl( String s ) throws RemoteException
          super();
          name = s;
     public String sayHello() throws RemoteException
          return "Hello World!";
     public static void main( String args[] )
          System.setSecurityManager( new RMISecurityManager() );
          try
               ServerImpl obj = new ServerImpl( "HelloServer" );
               // Naming.rebind("//myhost/HelloServer", obj);
               Naming.rebind( "rmi://ron:1099/HelloServer", obj );
               System.out.println( "HelloServer bound in registry" );
          catch ( Exception e )
               System.out.println( "HelloImp1 err: " + e.getMessage() );
               e.printStackTrace();
Help!

Hi,
Just try to rebind just the name of the interface to the server instance.
Naming.rebind("Hello",obj);
|->name of the interface.
--P

RMI callback error

We have a client that makes an RMI call. The server then tries to make a callback to the client. I know the client's call to the server succeeds, but when the server tries to make the callback, it gives the error below.
Until recently the callback worked most of the time, but now it errors most of the time. The few times it works is mostly late at night. Some here have speculated that the cause is related to the network load. We aren't going through any firewalls. Unfortunately I'm not the author of this code, I inherited it and I'm primarily a C++ programmer.
Does anyone have any suggestions?
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err:java.rmi.ConnectException: Connection refused to host: 10.8.96.207; nested exception is:
java.net.ConnectException: Operation timed out: connect
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err:java.net.ConnectException: Operation timed out: connect
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at java.net.PlainSocketImpl.socketConnect(Native Method)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at java.net.Socket.<init>(Socket.java:268)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at java.net.Socket.<init>(Socket.java:95)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:20)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:115)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:494)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:169)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:78)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at radar_jclient.RadarClientRemoteObjectImpl_Stub.loginResult(RadarClientRemoteObjectImpl_Stub.java:120)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at com.ourcompany.radar.radar_server.RadarServerImpl$Registerer.run(RadarServerImpl.java:131)
Sun Jan 09 20:25:13 MST 2005:ExecGroup-0:err: at com.ourcompany.radar.radar_util.RadarThreadPool$PooledThread.run(RadarThreadPool.java:86)

Mark
Is 10.8.96.207 the correct IP address for the client? Can this address be pinged from the server host?
If it can be pinged, I have to agree that it is network load, although you would need a huge load or a very erratic network to cause this problem (dropping of at least 3 SYN packets at increasing intervals). Are there now any bridges &c in the network that weren't there when it worked? or have any of the NICs changed? or any other network topology?

RMI Callback ConnectException

Hi,
I'm trying to get a RMI Callback running on 2 different machines. The client registers itself at the server who then calls a method on the client. Locally everything works fine, but when running the server on a different PC I get a ConnectException when trying to call the callback method on the client. Funnily enough, the IP to which the connection is refused is that of the server! Why does it try to connect to itself? No firewalls involved, policies okay, registry running... Tested already with two machines running the same OS and Java version.
What am I missing?
Thanks a lot!

I'm also facing the same problem. The application without callbacks runs without problem in one machine AND two different machines. but when i run those on different machines the app with callbacks fails. In this case the client program gives error. The IP address it looks to connect is correct in my case.
Lookup completed
Server said hello
Exception in CallbackClient: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.ConnectException: Connection refused to host: 192.168.0.199; nested exception is:
java.net.ConnectException: Connection refused

Connection refused to host: connection timed out

I have been struggling with this problem a couple of days now so I really hope someone can help me. I am trying to get rmi to work in a NAT environment. We use a firewall, so I have opened port 1099 and 2020 which I use as a fixed port for communication (just to be sure it is not a firewall thing); I use the following code:
//server
public class ComputeEngine extends UnicastRemoteObject
implements Compute
public ComputeEngine() throws RemoteException {
super();
public String getMessage() {
return "you have successfully connected to the server";
public static void main(String[] args) {
if (System.getSecurityManager() == null) {
System.setSecurityManager(new RMISecurityManager());
try {
String port = args[0];
try {
RMISocketFactory.setSocketFactory(new FixedPortRMISocketFactory(Integer.parseInt(port)));
} catch (IOException e) {
e.printStackTrace();
LocateRegistry.createRegistry( 1099 );
catch (RemoteException e1) {
e1.printStackTrace();
String name = "rmi://localhost/Compute";
try {
Compute engine = new ComputeEngine();
Naming.rebind(name, engine);
System.out.println("ComputeEngine bound");
while(true); //stay alive
} catch (Exception e) {
System.err.println("ComputeEngine exception: " + e.getMessage());
e.printStackTrace();
public Socket createSocket(String host, int port)
throws IOException {
System.out.println("creating socket to host : " + host + " on port " + port);
return new Socket(host, port);
* Create a server socket on the specified port (port 0 indicates
* an anonymous port) and writes out some debugging info
* @param port the port number
* @return the server socket on the specified port
* @exception IOException if an I/O error occurs during server socket
* creation
* @since JDK1.1
public ServerSocket createServerSocket(int port)
throws IOException {
port = (port == 0 ? portnumber : port);
System.out.println("creating ServerSocket on port " + port);
return new ServerSocket(port);
//client
public class ComputePi {
public static void main(String args[]) {
if (System.getSecurityManager() == null) {
System.setSecurityManager(new RMISecurityManager());
try {
String name = "rmi://" + args[0] + "/Compute";
Compute comp = (Compute) Naming.lookup(name);
System.out.println("connected to server");
System.out.println(comp.getMessage());
} catch (Exception e) {
System.err.println("ComputePi exception: " + e.getMessage());
e.printStackTrace();
I start the client with:
java -Djava.security.policy=policy.all -jar client.jar 194.2.4.6:1099
I start the server with:
java -Djava.rmi.server.codebase="file:/C:\RMI\\server.jar" -Djava.rmi.server.hostname="194.2.4.6" -Djava.security.policy=policy.all -jar server.jar 2020
As you can see I set the "-Djava.rmi.server.hostname" property which should be a solution to the NAT problem. However I keep getting the following exception!!??!!:
ComputePi exception: Connection refused to host: 194.2.4.6; nested exception is:
     java.net.ConnectException: Connection timed out: connect
java.rmi.ConnectException: Connection refused to host: 194.2.4.6; nested exception is:
     java.net.ConnectException: Connection timed out: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
     at sun.rmi.server.UnicastRef.newCall(Unknown Source)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at java.rmi.Naming.lookup(Unknown Source)
     at client.ComputePi.main(ComputePi.java:14)
Caused by: java.net.ConnectException: Connection timed out: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)
     ... 7 more
Can anyone help me with this, please??????
kind regards,
Christiaan

Yes, i can ping it from the client.
I have also noticed that when i run my server with the option -Djava.rmi.server.hostname=IP the applications stops automatically after a few minuts...
I'm not using nothing about codebase. I have the stub and skel classes in server and client machines..
I add the complete exception:
Client exception: java.rmi.ConnectException: Connection refused to host: external_IP; nested exception is:
java.net.ConnectException: Connection timed out: connect
java.rmi.ConnectException: Connection refused to host: external_IP; nested exception is:
java.net.ConnectException: Connection timed out: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
at example.hello.Server_Stub.sayHello(Unknown Source)
at example.hello.Client.main(Client.java:55)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:426)
at java.net.Socket.connect(Socket.java:376)
at java.net.Socket.<init>(Socket.java:291)
at java.net.Socket.<init>(Socket.java:119)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect
SocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMaster
SocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
... 5 more

RMI Callback Connection Refused Problem

Similar Messages

Maybe you are looking for