Today we tried implementing retry logic in the LoadRunner script as a work around to the READ_TIMEOUT and KM timeouts we keep getting.
The basic synchronization logic is this:
It puts the synchronization logic into a method that can recursively call itself to perform the designated number of retries.
If an exception occurs, we check to see if it is a SynchronizeException and if there are any retries left.
If so, the script logs the error, then waits for the timeout period before attempting to synchronize the failed sync group again.
If the sync group continues to fail, it will ultimately throw the exception when the retries are exhausted, rendering the entire synchronization a failure at that point.
SAP Knowlage Management System
SMP 3.0 Runtime
Web Services timeout
Axis library timeout , KBA , MOB-SDK , SAP Mobile SDK , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.