topic Long running gp task sort of fails in ArcGIS JavaScript Maps SDK Questions

Long running gp task sort of fails

KevinGooss — Mon, 25 Oct 2010 21:49:21 GMT

I have a long running gp task that is a python script exposed by as a gp tool over the js api.
When i execute the task it returns a dojo.io.script error saying the Timeout exceeded. However a few seconds later it does return the correct result.
Something on the server I think is causing the timeout error message to be returned which is firing the errcallback on the method call, instead of waiting for the true result to fire my callback method.
I have tried to modify the timeout settings in IIS, web.config, and web.config in the rest services config. I also bumped the server object idle times, tried both pooled and non-pooled and synchronous/asynch on the server object.
If I could just ignore the err callback and get the method to fire when the result came back i would be set but if i comment out the err callback the true callback never gets hit.
Is there some magical one minute setting in IIS or ags?
Any suggestions?

Re: Long running gp task sort of fails

derekswingley1 — Mon, 25 Oct 2010 23:51:27 GMT

Not sure if this is applicable but have you looked at esri.config.defaults.io.timeout?

Re: Long running gp task sort of fails

KevinGooss — Tue, 26 Oct 2010 12:43:56 GMT

That was precisely it. Thank you very much

Re: Long running gp task sort of fails

JeffMcCullough — Tue, 29 Mar 2011 17:45:13 GMT

Kevin,

I am now having the same exact problem, and I have tried all the solutions that you have tried. Can you tell me how you used esri.config.defaults.io.timeout in your code? Where did you place it? If I could see a sample of the code with it, that would be great!

Thanks!

Jeff McCullough

Re: Long running gp task sort of fails

HemingZhu — Tue, 29 Mar 2011 18:47:02 GMT

Kevin,

I am now having the same exact problem, and I have tried all the solutions that you have tried. Can you tell me how you used esri.config.defaults.io.timeout in your code? Where did you place it? If I could see a sample of the code with it, that would be great!

Thanks!

Jeff McCullough

If you set GP service Execution type as Asynchronous (on Parameters tab) and then its timeout property is controlled by The maximum time a client can use a service(on Pooling tab). you don't have to set esri.config.defaults.io.timeout. Just remember in API using GP.sumbitJob instead of GP.execute.

Re: Long running gp task sort of fails

JeffMcCullough — Thu, 07 Apr 2011 15:58:39 GMT

Thanks for the response. I am running asynchronous and I am using SubmitJob and I am still getting time out errors. When you say properly set, what do you mean? It currently is 600 secs and when I run this gp on Arcgis server, it runs fine, and there are no issues.

Any other suggestions?

Thanks!

Re: Long running gp task sort of fails

nidhiarora — Wed, 18 May 2011 09:32:33 GMT

Hi ,

I am also using asynch GP tak and Submit job . In the GP service tab in timeout session , i have set each parameter as 6000 sec . I have also set the value of esri.config.defaults.io.timeout=600;

but i still get the timeout exception.

Any ideas will be appreciated

regards,
Nidhi

Re: Long running gp task sort of fails

DallasShearer — Fri, 24 Feb 2012 17:14:05 GMT

looks to me that the setting for esri.config.defaults.io.timeout
is defined in milliseconds so setting it to esri.config.defaults.io.timeout = 600
is a .6 second timeout
I set mine to esri.config.defaults.io.timeout = 300000
to give me a 5 min timeout.