sun.rmi.transport.tcp.readTimeout not effective -


I have set sun.rmi.transport.tcp.readtimeout as JVM parameter in my product's configuration file Available as a service, I have set a very low price of 1000ms, which means that all CLIs will take more than 1 second using all CLIs, with the exception should be unsuccessful. Java.rmi.ConnectIOException: error during JRMP connection installation; The nested exception is: read the deadline on java.net.SocketTimeoutException: sun.rmi.transport.tcp.TCPChannel.createConnection

Please tell me if I have not found any other parameters that do this work essential for . I want to set a time limit of 10 minutes to say. But I want to set a low value to ensure that the timeout is effective, is this parameter related to java.rmi.activation.port and java.rmi.server.hostname? please look.

Which means that taking all the functions that used my CLI more than 1 second Not a failure.

No it is not a client-side timeout can do this, but read sun.rmi.transport.tcp.readTimeout from time to time on the server, which has an effect on connection pooling. To control time-consuming client-side reading, you need to set an inappropriate property called Sun.Romie.portport.tccp.responseTimeout (I think) on each client JVM.

Comments