RMI-server works on Windows and Linux but not on Solaris

Question

I wrote an application which uses RMI. The server is successfully tested on Windows and Linux. However it doesn't work on Solaris.
Naming.lookup works, I can find the server. But calling a method on my remote interface causes a ConnectionException:
java.rmi.ConnectException: Connection refused to host: 192.168.1.123; 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.newCall(Unknown Source)
     at at.triton.javaengine.server.ServerImpl_Stub.connectToWindow(Unknown Source)
     at at.triton.javaengine.client.JavaEngineClient.connectToWindow(JavaEngineClient.java:288)
     at at.triton.javaengine.client.JavaEngineClient.main(JavaEngineClient.java:787)
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)
     ... 7 moreNote that I have almost no experience with Solaris.
Additional information about the common pitfalls which I have already checked:
* rmiregistry finds the server classes (the exception was different without them)
* the server is in the LAN and the desktop firewall of the client is double-checked to let the required ports through to any destination.

Answer 1

java.rmi.ConnectException: Connection refused tohost: >192.168.1.123; nested exception is:
java.net.ConnectException: Connection refused:
: connect
Clearly indicates what is happening inside there.Clearly indicates that you don't know what you are talking about.
Any applications invoked with a security manager must
be granted explicit permission to access local system
resources apart from read access to the directory and
its subdirectories where the program is invoked.Any application that gets a java.net.ConnectionException: Connection
refused is getting it more or less directly from the TCP/IP stack. If the problem had anything to do with policies and permissions and SecurityManagers, it would have been an AccessControlException .
if your client RMI doesnt include these lines then If your 'client RMI' does include these lines then I would like a definition of what exactly a 'client RMI' really is, because I've been using RMI for ten years and wrote a book about it and I certainly don't know.
1)just include these lines
if (System.getSecurityManager() == null) {
System.setSecurityManager(new
SecurityManager());In other words, if the application doesn't already have a security manager, in which case the contents of the policy file or the 'client RMI', or whatever you want to call it, are completely irrelevant, such that they couldn't possibly be having the problem you desrcribe, add a security manager so that we get into the land where you might possibly know what you're talking about?
e a policy file
grant {
permission java.net.SocketPermission
"192.168.1.123:1099", "accept,connect,resolve";
};And this is completely unnecessary if there isn't a security manager, and completely unrelated to the OP's problem.