CODEWITHSUNDEEP
javarmi
Sidd
Sidd

Reputation: 333

error with JRMP connection establishment

I am getting following exception trace :

java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: 
    java.net.SocketTimeoutException: Read timed out
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:293)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:190)

I read some forums on this but not getting clarity on the root cause of this exception. Is this due to one of the following reasons?

  1. Insufficient memory.
  2. RMI calls getting failed due to increased number of requests to the server causing one of them to wait and causing time outs for this request to process.
  3. Incompatible jre version or anything related to JRE version.
  4. Any networking related issue.
  5. Firewall related.

Upvotes: 16

Views: 60741

Answers (3)

timguy
timguy

Reputation: 2582

I have the same error at client side. Server is reachable and I can open the port via telnet. When I watched into it with Wireshark on client and server side I see the following:

  • TCP connection is established

  • SYN

  • SYN, ACK

  • ACK

  • Client sends: JRMI, Version 2, Stream Protocol

  • Server reply: JRMI, ProtocolAck - But this package never reached client side

In my case issue is the connection from MagicDraw client to license server. For other colleages at other locations it helps to use the proxy: http.proxyHost=xxxx -Dhttp.proxyPort=8080 and the client communicats via HTTP. So maybe this could help you to ommit this issue. https://docs.oracle.com/javase/7/docs/platform/rmi/spec/rmi-arch6.html

I can not be specific as I don't have access to the source code of Magic Draw.

Upvotes: 3

Jochen Seliger
Jochen Seliger

Reputation: 1

I get this error in the case, when a SSH-Client from outside the LAN, holding the SSH-Server, is trying to connect to the server and RMI is involved to let the client execute RMI-methods on the server. The reason is the unreachability (missing route) of the server. Seems that all the stated cases are related to that reason.

Upvotes: 0

user207421
user207421

Reputation: 310903

  1. Insufficient memory.

Not at the client. Possibly at the server, if it causes a failure to allocate a thread for example.

  1. RMI calls getting failed due to increased number of requests to the server causing one of them to wait and causing time outs for this request to process.

No. The error occurs during the connection establishment phase, long before the server-side method implementation gets invoked.

  1. incompatible jre version or anything related to JRE version.

No.

  1. Any networking related issue.

Yes.

  1. Firewall related.

No. That would cause a connect timeout, or in certain obsolete cases a connection refusal, not a read timeout.

Upvotes: 4

Related Questions