[Soaplab-users] timeout settings and waitFor calls
Brought to you by:
marsenger
From: <ul...@eb...> - 2009-01-15 09:55:13
|
Hi, I have recently learned that we need to be more cautious when using runAndWaitFor and the waitFor methods in Soaplab interface. Soaplab web applications by default has a connection timeout setting of 5 minutes. Also some Soaplab servers may have load-balancer layers that may in turn have a maximum reply time setting, as for the EBI Soaplab server. In my recent experiences with jobs requiring time longer than the maximum reply time setting of the EBI Soaplab server the error messages returned after the maximum reply time was not clear enough to reveal that my waitFor calls was returning due to maximum reply time timeout. If you were getting error messages for your Soaplab calls after waiting couple of minutes and the error messages was not clear enough to understand the reason then it is possible that your calls may have been interrupted due to one of the timeout settings. If you want to make sure that you don't want to hit timeout limits an alternative would be to use createAndRun->getStatus->getResults series of calls rather than the createAndRun->waitFor calls or the runAndWaitFor call. Regards, Mahmut |