Secure Connect Client - Timeout functionality (4037234)

SocketTimeout –  This value is directly passed to setSendTimeout function which controls when the blocking call on the socket should return in case I/O is not successful. Minimum value is 0 which means block until I/O operation is successful. This may cause the application to hang. There is no maximum value defined, but it should be reasonable so that application waits for sufficient time to le the I/O happen. If the value is too high, application will be blocked for so much time.

ReconnectTimeout – if this is set to 0, no reconnections are done so even a short network glitch will reset the connection between the application and QoreStor. The value should not be  set to more than 1800 seconds, because if the network is up even in 30 minutes then it means it is some permanent outage and reconnections will never be successful. 

Following is the timeline with default settings which are good most of the environments and these should not be changed unless these are not suitable for that specific environment.

T₁ – Read/write request issued on socket

T₂(after 60 seconds) – Socket times out and it will enter reconnection mode

T₃ – Try reconnecting  

T₄ – Try reconnecting

:

T_n (10 minutes since T₂)- if the connection still could not be established, reconnections are stopped and application will be notified of the error.