Hello,

The important line in your stacktrace is
org.mmbase.bridge.remote.implementation.RemoteCloudContext_Impl.getCloud (RemoteCloudContext_Impl.java:

It actually says that it could retrieve the CloudContext from the RMIRegistry, but it failed to get a connection to the stub object. The RMIRegistry only stores an url to the stub. This url is usually your hostname with port one higher than the rmiregistry port. It seems you can't connect to that one. The RMIRegistryServer in rmmci.xml was intended to make sure what the hostname was, but I found a small error in the RMMCI code the other day which fails to do that. The RMIRegistryServer should have set the system property java.rmi.server.hostname, but that does not happen. This will happen when the mmbaseroot.xml hostname is set or when it is passed to the jvm with -Djava.rmi.server.hostname=localhost. The latter one should always work.

Nico

Zhang Xiaofei wrote:

Hi,all

I met a troublesome error which cost me two days. I still don't get method to solve it now. I am really confused. When I use RMMCI module in my own pc, this error appears as blow. but when I connect to my friend's pc with tomcat5.5+mmbase1.8.4+mysql5(which is as same as my computer), it works very well.

Could you give me some suggestions about this error, and how to solve it. Thank you:-)
Hope to hear from you soon.

Best wishes.

Eddy


The Error generated by eclipse:
Exception in thread "main" org.mmbase.bridge.BridgeException: Connection refused to host: 10.1.1.102 <http://10.1.1.102>; nested exception is:
    java.net.ConnectException: Connection refused: connect
at org.mmbase.bridge.remote.implementation.RemoteCloudContext_Impl.getCloud(RemoteCloudContext_Impl.java:77) at org.seaba.scheduler.jobs.mail.EmailSenderTest .<init>(EmailSenderTest.java:46)
    at org.seaba.scheduler.jobs.mail.Test.main(Test.java:5)
Caused by: java.rmi.ConnectException: Connection refused to host: 10.1.1.102 <http://10.1.1.102>; nested exception is:
    java.net.ConnectException: Connection refused: 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.invoke(Unknown Source)
at org.mmbase.bridge.remote.rmi.RemoteCloudContext_Rmi_Stub.getCloud(Unknown Source) at org.mmbase.bridge.remote.implementation.RemoteCloudContext_Impl.getCloud (RemoteCloudContext_Impl.java:74)
    ... 2 more
Caused by: java.net.ConnectException: Connection refused: 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.SocksSocketImpl.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)
    ... 8 more

------------------------------------------------------------------------

_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers

_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers

Reply via email to