Setting the RMI Connection Timeout Duration
In case of low bandwidth or high latency network environment, the RMI threads from the PTC RV&S client application may get blocked for longer duration while connecting to the main server. Depending on the network bandwidth or latency, you can adjust the value of the following property:
IntegrityClient.rmi.connectiontimeout: This property specifies the timeout duration in seconds for RMI thread from the PTC RV&S client application to the PTC RV&S server. Setting the value to 0 disables the timeout and the application threads wait indefinitely till the connection with the server is successful.
On a PTC RV&S client application the connection timeout is disabled by default even if the default value is set to 60 seconds. To enable the timeout on the PTC RV&S client, set the IntegrityClient.rmi.enableConnectionTimeout property to true. This property is only applicable to the PTC RV&S client.
Connection Attempts
On a PTC RV&S client, the property IntegrityClient.rmi.connectionRetryCount specifies the maximum number of connections attempts an application makes when connecting with the PTC RV&S client, the PTC RV&S proxy server, and the PTC RV&S main server. If the connection attempts exceed the retry count, the application assumes that it is not able to connect to the client, proxy server, and the main server.
* 
If value for the property is not specified or is set to 0, then the retry count is disabled and only a single connection attempt is made.
The retry count is ignored if the connection timeout is disabled. In this case the following properties do not have any impact on the system:
The IntegrityClient.rmi.connectiontimeout client property.
The mksis.rmi.connectiontimeout server or proxy server property.
Was this helpful?