RMI Protocol over JRMP transport: connection refused to host: 10.10.10.10

Hi,
We migrated our Discoverer 9.0.2 to 10.1.2. However, when we connected to Discoverer Plus, the message saying "RMI Protocol over JRMP transport: connection refused to host: 10.10.10.10" appeared. We use the "Default" communication protocol and Sun JVM 1.4+ is installed in the client. Do you know what's happening?
Thanks.
Andy

Hi Andy
It could be a Java incompatibility issue. On one of your client machines try removing Java altogether and then reconnecting to Discoverer Plus. The server should send down a new, clean version of the Java.
Try this and let me know how you get on
Best wishes
Michael

Similar Messages

RMI Protocol over JRMP transport: connection refused

I changed the look and feel for disco plus to Jinitiator. I then started getting error RMI Protocol over JRMP transport: connection refused to host: 192.168.1.1
I changed the settings back to java plugin 1.4 but I'm still getting the same error on all client machines.
I'm running windows 2003 and application server 10.1.2.0.2
Thanks for any help,
Brian

Hi Brian
When you changed to JInitiator what did you set the style to be? Also, why would you not want to use the Sun Java?
Anyhow, try getting the users to clear their local Sun Java cache, this will release the applet causing it to reload upon next connection, and try again.
If you want to retry JInitiator, try this:
1. Go to Control Panel | JInitiator 1.3.1.x or whatever version you are using
2. Navigate to the Proxies tab
3. Uncheck Use Browser Settings
4. Click the Apply button
5. Close all browser windows
6. Reconnect to Discoverer Plus
If the above steps do not help, try editing the security details of the Options menu in the Internet Explorer using this workflow:
1. On the client machine, launch IE
2. From the toolbar, select Tools | Internet Options
3. Navigate to the Security tab
4. Click on the Trusted Sites icon
5. Click on the Sites button
6. Add a fully, qualified HTTP link to your server
7. Close all browser windows
8. Reconnect to Discoverer Plus
Of the two solutions above, the first is most likely to fix your issue. However, I advise all my customers to set up the application server connections as being trusted sites.
One additional thing would be to delete your cookies. Discoverer Plus loves cookies.
Best wishes
Michael

RMI protocol over JRMP transport error when accessing Discoverer Plus

Hi,
I just upgraded my Discoverer to 9.0.2.54.01. I can successfully access my Discoverer Viewer Workbooks but not my Discoverer Plus. When I try to access Plus, Applet will be started, and then it will prompt the RMI protocol error:
Attempt 1. RMI protocol over JRMP transport: Connection refused to host: 127.0.0.1; nested exception is:*
java.net.ConnectException: Connection refused: connect*
Attempt 2. RMI protocol over http transport : Unable to attach to existing session.*
I used browsers Mozilla3.0.5 and IE7.
Thanks!

Hi Andy
It could be a Java incompatibility issue. On one of your client machines try removing Java altogether and then reconnecting to Discoverer Plus. The server should send down a new, clean version of the Java.
Try this and let me know how you get on
Best wishes
Michael

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.

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

Help me pls in ConnectException: Connection refused to host

hi all,
i'm getting the following exception could any one help me out from this.
i have opened two particular ports that r listening for RMI
C:\j2sdk1.4.0-rc\bin\Test>java -Djava.security.policy=allper.policy CallClient
java.rmi.ConnectException: Connection refused to host: xxx.xxx.xxx.xxx; nested ex
ception 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.newCall(UnicastRef.java:313)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at java.rmi.Naming.lookup(Naming.java:83)
at Client.add(Client.java:146)
at CallClient.main(CallClient.java:47)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148)
at java.net.Socket.connect(Socket.java:425)
at java.net.Socket.connect(Socket.java:375)
at java.net.Socket.<init>(Socket.java:290)
at java.net.Socket.<init>(Socket.java:118)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22) at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:122)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
... 7 more
looking for ur help
-shafeeq

hi,
actually it is giving syntax error if i include like this in the client code
systemProperties.put("sun.rmi.transport.connectTimeout",15000);
systemProperties.put("sun.rmi.server.disableHttp","false");
pls guide me how exactly i should include in the client codings.
pls help
-shafeeq
Note: from http://java.sun.com/j2se/1.4/docs/guide/rmi/sunrmiproperties.html/#connectionTimeout
sun.rmi.transport.proxy.connectTimeout (1.1 and later)
The value of this property represents the maximum length of time (in milliseconds) that the RMI runtime will wait for a connection attempt (createSocket) to complete, before attempting to contact the server using HTTP. This property is only used when the http.proxyHost property is set and the value of java.rmi.server.disableHttp is false. The default value is 15000 milliseconds (15 seconds).

Connection refused to host 127.0.0.1 (Lookup windows -- Linux)

Hi Folks,
Buddies I am facing a problem. My server is running at specified port on a linux machine but when I try to connect it from a windows machine i got error massage "Connection refused to host 127.0.0.1 " but it's very inscrutable message.
I made some changes in /etc/hosts file and /etc/xinetd.d/services and everything worked fine.
But now there is a question come in my mind that , Is there any alternative so we don't need to make any change in above mentioned two files.
My Changes;
/etc/host
I've added system ip and name in the first line.
/etc/xinetd.d/services
Modified services files and enabled protocol and permitted to all system who are under class three network.
Could anybody have a better idead to avoid these changes because of security issues?
--Manoj

Hi,,,Thanks
When I refer to random it is when the pc in windows in his configuration of net it has " obtain ip automatic " when the ip are fixed in the configuration of net I do not have problems of (connection refused to host:name_machine) what I need is to know that I must do to solve the problem (connection refused to host:name_machine) when in the pc they have a configuration of net of obtaining ip automaticamennte,
I dont understand when you say that..."you should always set java.rmi.server.hostname at server JVMs to the FQDN of the host, not the IP address." Where I do this ??, where I put it??, I dont understand
you can help me to know if this could solve my problem when the ip is obtained automatically
this it is my code...
public static UserPreferences systemPrefs;
static
try
Configuration cfgServer = (Configuration) Registry.lookupServer(Configuration.class);
systemPrefs = cfgServer.getSystemPreferences();
catch (Exception e)
Logger log = LoggerFactory.getLogger(AlertManagerServer.class);
log.error("Error obteniendo las preferencias para Alert Manager Client", e);
/** Puerto **/
public static final String SERVER_PORT = systemPrefs.getString(SystemModuleDescriptor.Settings.ALERTMANAGER_SERVER_PORT, "1198");
/** Server Name **/
public static final String SERVER_NAME = NotificationConstants.ALERTSERVER_NAME;
/** Client Separator **/
public static final String ALERTCLIENT_SEPARATOR = NotificationConstants.ALERTCLIENT_SEPARATOR;
* Constructor
public AbstractAlertManagerClient()
* Constructor
* @param clientName Nombre del cliente
* @throws Exception Problemas
public AbstractAlertManagerClient(String clientName)
throws Exception
launchClient(clientName);
* Subiendo el Cliente de Mensajeria
* @param clientName Nombre
* @throws ProvisioningException Problemas
public void launchClient(String clientName)
throws ProvisioningException
try
NotificationInterface notification = (NotificationInterface)Registry.lookupServer(NotificationInterface.class);
String serverIPAddress = notification.getServerIPAddress();
String serverInfo = "//" + serverIPAddress + ":" + SERVER_PORT + "/" + SERVER_NAME;
AlertManagerServerInterface server = (AlertManagerServerInterface) TransparentItemProxy.getItem( serverInfo,new Class[] { AlertManagerServerInterface.class });
AlertManagerClient client = new AlertManagerClient();
this.server = server;
this.name = setClientName(clientName);
client.server = server;
client.name = setClientName(clientName);
Object oclient1 = new Remote(this);
oclient = oclient1;
Remote.invoke(server, "registerClient", oclient1);
catch(Exception ex)
String msg = "";
msg += "[ERROR] trying com.iptotal.notification.bo.AbstractAlertManagerClient.AbstractAlertManagerClient()...subiendo Client ";
ProvisioningException pex = new ProvisioningException(ProvisioningException.ErrorCatalog.NOTIFICATION_DISPATCHING_ERROR, ex);
Logger log = LoggerFactory.getLogger(AbstractAlertManagerClient.class);
log.error(msg, pex);
throw pex;
* Registrar un Cliente
* @param client Cliente
public void registerClient(Object client)
try
String name = (String)Remote.invoke(client,"getClientName",null);
if( ! clients.containsKey(name) )
clients.put( name, client);
catch(Exception ex)
String msg = "";
msg += "[ERROR] trying com.iptotal.notification.bo.AlertManagerServer.registerClient(1) ";
Logger log = LoggerFactory.getLogger(AlertManagerServer.class);
log.error(msg + " " + ex.getMessage()); // VA: para que no salgan en el log los stacktrace del CAJO no route to host
Really Thank you for the help that you can offer me

Error in test connection: Connection refused to host: 172.22.100.77

Hi,
I'm trying to connect B1if to a SBO DB in a different server that dosen't have B1if instaled.
I'm getting this error:
XCE001 Nested exception: java.rmi.RemoteException: com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: java.rmi.ConnectException: Connection refused to host: 172.22.100.77; nested exception is:
java.net.ConnectException: Connection refused: connect
Best Regards,
Ana Silva

Hi,
B1if is only a framework. Both db should install the framework.

Connection refused by host in Nagios NRPE

Hi Experts
I had configured Nagios in Redhat linux everthing is working smoothly
My problem is i have Solaris 8,9,10 now i am installing NRPE plugings and NRPE in Solaris 10 to get the details of swap space & Machine load information all the compilation went smoothly.
When i run the given below command i am getting connection refused by host.
bash-2.05# /usr/local/nagios/libexec/check_nrpe -H 127.0.0.1
Connection refused by host
One more query how to start xinetd in solaris10 and other solaris platform.I saw in nagios NRPE document it says to run "make install-xinetd" if it is there how to start it i think most probly xinet is not running
Could any please help me on this
Thanks
kr

Describe your setup and what internet realated applications you've installed and i'm sure someone will be able to help you.
- How are you connecting - via a swtich, usb or ethernet modem somehow?
- What other apps are installed - any download managers or things that integrate with your web browser?

How to intercept RMI calls over JRMP?

Hi,
I would like intercept calls over RMI/JRMP to pass contextual data between client and server. I was able to do it for IIOP using Portable Interceptor but could not find any solution for JRMP.
Is there any other way to implicitly pass data between client and server?
Thanks,
Kapil

Not in JRMP. See JERI in the Jini project for an extensible protocol.
If you want full-strength RMI proxying see http://www.rmiproxy.com and contact me via the links there for more information on recently-developed products that address this need.
Esmond Pitt

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.

Connection Refused -RMI over the internt

Hi All
I have been looking at posts in the forums to solve my problem and now reached a kind of dead end hope someone can help.
I have this RMI application that was desigend to run over a network and it works fine.It was decided that it should be used over the internet. Running as is started the problems ( as expected)
what happened initially was that client would make a connection to the server but would throw an exception when server tried to callback the client.
The forums solution was to have 2 ports opened ( like 1098 and 1099) and connect which I did. This caused a new problem now the client itslef throws a connection exception.
This led me to belive that there would be a networking issue but the netadmin reports that he is seeing traffic reach the server and packets sent back. However I see an exception that is Connection refused to host : <IPADDRESS OF THE SERVER> :connection timed out
Any help would be much appreciated
Thanks

I followed ejp's instructions and everything worked perfectly. Here is a bit more detailed explanation of what I did.
I've been having various problems implementing an RMI Server/Client architecture, with Client Callbacks. My scenario is that both Server and Client are behind Firewall/NAT. In the end I got a fully working implementation. Here are the main things that I did:
Server Side , Local IP: 192.168.1.10. Public (Internet) IP 80.80.80.10
On the Firewall/Router/Local Server PC open port 6620.
On the Router/NAT redirect incoming connections on port 6620 to 192.168.1.10:6620
In the actual program:
System.getProperties().put("java.rmi.server.hostname", IP 80.80.80.10);
UnicastRemoteObject.exportObject(this, 6620);
Client Side, Local IP: 10.0.1.123 Public (Internet) IP 70.70.70.20
On the Firewall/Router/Local Server PC open port 1999.
On the Router/NAT redirect incoming connections on port 1999 to 10.0.1.123:1999
In the actual program:
System.getProperties().put("java.rmi.server.hostname", 70.70.70.20);
UnicastRemoteObject.exportObject(this, 1999);
Hope this helps.
Iraklis

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.

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

RMI Protocol over JRMP transport: connection refused to host: 10.10.10.10

Similar Messages

Maybe you are looking for