Geoprocessor activity timeout error

Permanently deleted user

2. November 2018 15:34

Hi,

 

I have a workflow that has geoprocessor activity to run a GP service. It is Synchronous GP service. But I am getting an error when the workflow is taking a bit longer time like around 100 seconds or more. I configured the web config file in Rest folder and HTML Viewer files with 6 minute timout value. Unable to findout why it is getting timed out. Need help if there is any location where we should configure to work around the timout error.

 

System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse() at ESRI.ArcGIS.Client.WebRequest.UploadString(Uri url, String data, ICredentials credentials, X509Certificate clientCertificate) at ESRI.ArcGIS.Client.WebRequest.Request(ICredentials credentials, X509Certificate clientCertificate) at ESRI.ArcGIS.Client.Tasks.TaskBase.Request(String url, Dictionary`2 parameters, Boolean forcePost, Boolean getString) at ESRI.ArcGIS.Client.Tasks.Geoprocessor.Execute(List`1 parameters) at Geocortex.Workflow.Activities.Geoprocessor.ExecuteGeoprocessorSync(NativeActivityContext context, Geoprocessor geoprocessor, List`1 parameters) at System.Activities.NativeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

0

• 

  Aaron Oxley

  7. November 2018 19:22

  Hi Shubham,

   

  This is a tough one to diagnose through the forums, timing of web requests usually requires in-depth troubleshooting. My initial thoughts are a possible incompatibility between Java on Essentials and ArcGIS Server, or a proxy causing delays due to slow authentication processing. 

   

  I recommend using Fiddler or a similar web traffic recording tool to analyze the communication from both ends. If that does not provide clues as to what is causing the issue, my next suggestion is to get help from a support analyst - open a support case by contacting us at support@geocortex.com. 

   

  Thanks,

   

  Aaron Oxley

  0
• 

  Permanently deleted user

  27. November 2018 10:36

  Hi,

   

  We were not able to narrowdown on the issue yet. As a workaround we started using Web Request Activity instead of Geoprocessor activity in our workflow and things are running smoothly. Clearly something is problem with the Geoprocessor activity not reading the timout value from web.config.

   

  - Shubham

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.