Hello,
We are utilizing a VersionOne<->ALM integration that gets an occasional runtime error. This integration application from VersionOne keeps open all project connections during runtime.
What I am trying to do is shore up the integration's connectivity robustness a bit since our integration application is running out of the US while the ALM server farm is in Germany. It certainly appears as though network connectivity or available bandwidth is the issue here as the integration runs fine for quite some time until failure (8 days being the most recent uptime).
Polling (asking ALM projects for information) takes place on a 5 minute interval . The time between failures is not very consistent so I am leaning towards a bandwidth issue that may be the result of an OTAClient request for connectivity status that takes too long to return.
So in order to fine tune this robustness update, how long of a timeout is it before connectivity status requests (e.g. TDConnection object's request for ITDConnection.Connected, LoggedIn or ProjectConnected) before the COMEXception message 'Server is not available" will be reported?
This being for ALM 11.52, FYI.