Troubleshooting
Problem
Attempts to perform a silent install of an IBM Rational product through a remote repository using Installation Manager results in the error "Resumable download failed" or "java.net.SocketTimeoutException: Read timed out".
Symptom
The GUI installation works fine and shows that the repository itself is healthy.
Cause
In GUI mode, Installation Manager will retry the network timeouts indicated by: 'java.net.SocketTimeoutException: Read Timed out' until user decides to cancel.
Diagnosing The Problem
Verify there is not a network problem to address.
Resolving The Problem
Reconfigure the Installation Manager preferences to allow silent mode to report a problem in less time.
In silent install mode, Installation Manager retries the network connection only for a limited number of times.
The associated preferences are:
- com.ibm.cic.common.core.preferences.connectTimeout=30
- com.ibm.cic.common.core.preferences.readTimeout=30
- com.ibm.cic.common.core.preferences.downloadAutoRetryCount=0
Preferences are described in the Installation Manager InfoCenter:
http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp
- The timeouts are in seconds.
- These are low level timeouts.
- The first level of retries will retry timeouts for 3 times.
During silent install the next level of retries is determined by 'downloadAutoRetryCount' preference:
- The value 0 is special and means that a single retry is attempted right away.
- Value greater than 0 set the number of higher level retries.
- These are each performed after a waiting period of 1 minute.
Setting 'downloadAutoRetryCount' higher than 3 and increasing the timeout values should resolve latency issues during silent installs.
Here is an example of setting downloadAutoRetryCount to 5 and keep the timeouts unchanged at 30 seconds.
After 3 lower level retries, 4 network calls have been made which add up to approximately 2 minutes. This is repeated 5 times after a waiting period of 1 minutes each. This would give a total of (first attempt + 5 retries) * (waiting period + lower level timeouts) = 6 * (1 + 2) = 18 minutes.
So with these settings, it would take Installation Manager up to 18 minutes before accepting failure.
Was this topic helpful?
Document Information
Modified date:
25 October 2021
UID
swg21418662