Matthew Farrellee wrote:
Doesn't that seem small? I can understand that a typical use case would be to submit a job and monitor that job over web services using the clusterId and jobId, but looking up jobs from a queue that has 10's of thousands of jobs would timeout. Any reason why this shouldn't be parameterized?Jason Reilly wrote:Hi, Is there a way to change/configure connection timeout on the server side for web service calls? I can't seem to find anything pertaining to this in the manual. Thanks, jdrHave a look at src/condor_daemon_core.V6/soap_core.cpp. The timeouts are not configurable, and set to 20 seconds for sending and receiving data.
begin:vcard fn:Jason Reilly n:Reilly;Jason email;internet:jdr0887@xxxxxxxxx tel;work:9194459686 x-mozilla-html:FALSE version:2.1 end:vcard