gp service times out after 10 minutes

1199
4
Jump to solution
11-01-2018 02:29 AM
Robertvan_Gilst
New Contributor III

Hi,

My GP service times out after approximately 10 minutes. I've increased "The maximum time a client can use a service" to 2400 seconds, but this value is not honored.

When I set the value low, I get the following error when the timeout period is met:

  • esriJobMessageTypeInformative: java.lang.Exception: Processing request took longer than the usage timeout for service 'Pipelog/pipelog.GPServer'.

When I set the value to 2400 seconds after approximately 10 minutes it fails like this:

  • esriJobMessageTypeInformative: Processing request took longer than the usage timeout for service 'Pipelog/pipelog.GPServer'.

It looks like there are two different timeout settings, but I only know how to set the timeout threshold on the GP Service.

Someone experienced the same challenge as I have? And hopefully a solution for this.

Robert

0 Kudos
1 Solution

Accepted Solutions
Robertvan_Gilst
New Contributor III

Forgot to mention that is was on a ArcGIS Server 10.6

The problem went away after we installed all existing patches until this moment (I am not sure which one solved the problem.)

View solution in original post

4 Replies
JonathanQuinn
Esri Frequent Contributor

Hm, it is strange that you see different messages, but what is taking the longest? Can you add arcpy.AddMessage statements to see where it's hung up? I'd say the exception with java.lang.Exception is likely timing out as it makes it into the Server, while the message without it made it in, but times out when it's running. You may be seeing it timeout as it makes it in as all instances are being used, (since the ones that are running are hung), so you're seeing two separate timeouts. I'd start by adding statements to sort out where it's hung. You'll need to set the GP service to return INFO messages.

0 Kudos
Robertvan_Gilst
New Contributor III

After I posted yesterday I created a new service which runs the following:

runner = 0
while runner < 30:
   arcpy.AddMessage("Run {}".format(runner))
   time.sleep(60)
   runner += 1
‍‍‍‍‍

And noticed the following behavior:

After approximately 10 minutes:

Job Details: j01d59f56600943ff8bb75d8cbc9445dd (Dummy)

Job ID: j01d59f56600943ff8bb75d8cbc9445dd

Job Status: esriJobFailed

Job Messages:

  • esriJobMessageTypeInformative: Submitted.
  • esriJobMessageTypeInformative: Executing...
  • esriJobMessageTypeInformative: Executing (Dummy): DummyTool
  • esriJobMessageTypeInformative: Start Time: Thu Nov 1 15:42:09 2018
  • esriJobMessageTypeInformative: Running script DummyTool...
  • esriJobMessageTypeInformative: Run 0
  • esriJobMessageTypeInformative: Run 1
  • esriJobMessageTypeInformative: Run 2
  • esriJobMessageTypeInformative: Run 3
  • esriJobMessageTypeInformative: Run 4
  • esriJobMessageTypeInformative: Run 5
  • esriJobMessageTypeInformative: Run 6
  • esriJobMessageTypeInformative: Run 7
  • esriJobMessageTypeInformative: Run 8
  • esriJobMessageTypeInformative: Run 9
  • esriJobMessageTypeInformative: Run 10
  • esriJobMessageTypeError: Failed.
  • esriJobMessageTypeInformative: Processing request took longer than the usage timeout for service 'Pipelog/pipelog.GPServer'.

But after pressing refresh I could see that the job was continuing to the end of the script:

Job Details: j01d59f56600943ff8bb75d8cbc9445dd (Dummy)

Job ID: j01d59f56600943ff8bb75d8cbc9445dd

Job Status: esriJobFailed

Job Messages:

  • esriJobMessageTypeInformative: Submitted.
  • esriJobMessageTypeInformative: Executing...
  • esriJobMessageTypeInformative: Executing (Dummy): DummyTool
  • esriJobMessageTypeInformative: Start Time: Thu Nov 1 15:42:09 2018
  • esriJobMessageTypeInformative: Running script DummyTool...
  • esriJobMessageTypeInformative: Run 0
  • esriJobMessageTypeInformative: Run 1
  • esriJobMessageTypeInformative: Run 2
  • esriJobMessageTypeInformative: Run 3
  • esriJobMessageTypeInformative: Run 4
  • esriJobMessageTypeInformative: Run 5
  • esriJobMessageTypeInformative: Run 6
  • esriJobMessageTypeInformative: Run 7
  • esriJobMessageTypeInformative: Run 8
  • esriJobMessageTypeInformative: Run 9
  • esriJobMessageTypeInformative: Run 10
  • esriJobMessageTypeError: Failed.
  • esriJobMessageTypeInformative: Processing request took longer than the usage timeout for service 'Pipelog/pipelog.GPServer'.
  • esriJobMessageTypeInformative: Run 11
  • esriJobMessageTypeInformative: Run 12
  • esriJobMessageTypeInformative: Run 13
  • esriJobMessageTypeInformative: Run 14
  • esriJobMessageTypeInformative: Run 15
  • esriJobMessageTypeInformative: Run 16
  • esriJobMessageTypeInformative: Run 17
  • esriJobMessageTypeInformative: Run 18
  • esriJobMessageTypeInformative: Run 19
  • esriJobMessageTypeInformative: Run 20
  • esriJobMessageTypeInformative: Run 21
  • esriJobMessageTypeInformative: Run 22
  • esriJobMessageTypeInformative: Run 23
  • esriJobMessageTypeInformative: Run 24
  • esriJobMessageTypeInformative: Run 25
  • esriJobMessageTypeInformative: Run 26
  • esriJobMessageTypeInformative: Run 27
  • esriJobMessageTypeInformative: Run 28
  • esriJobMessageTypeInformative: Run 29
  • esriJobMessageTypeInformative: Completed script DummyTool...
  • esriJobMessageTypeInformative: Succeeded at Thu Nov 1 16:12:10 2018 (Elapsed Time: 30 minutes 0 seconds)

Job Status says failed but the last message says succeeded. I think it's a bug and will report this to Esri.

By the way, when I set the timeout to less than 10 minutes, the job is terminated after the time period.

Robert

0 Kudos
Robertvan_Gilst
New Contributor III

Forgot to mention that is was on a ArcGIS Server 10.6

The problem went away after we installed all existing patches until this moment (I am not sure which one solved the problem.)

View solution in original post

Juan_FelipeMonsalve_Osorio
New Contributor

Hola,

Yo tuve el mismo problema, en mi caso tengo un ArGIS 10.6 en un MWS 2012 R2 Std. 

El parche que soluciono el problema fue Parche de inicio del servicio de geoprocesamiento de ArcGIS Server

0 Kudos