timeout settings not propagated

Permanently deleted user

May 14, 2018 08:40

Hello

 

I am attempting to get our GE cluster to timeout after 2 minutes (the IIS default)  instead of 1 minute.

 

I have changed the timeout in the viewer using the snippet, as described in previous KB article (Increase Timeout for running workflows) and also added the timeout setting to the REST end web.config on the three servers in our GE cluster.

 

By deliberately running the browser in modem speed mode I can get the viewer to timeout on site load, but it only has a timeout of 1 minute.

 

Our clients single server timeout has been successfully changed to 2 minutes, by making the changes described in the KB article, and testing the same way.

 

Can you tell me if there is another place I should change something for this cluster to have a 2 minute timeout.

 

Thanks

 

 

 

 

0

• 

  Permanently deleted user

  October 03, 2018 20:49

  Hi Roland,

   

  If you're clustering Geocortex Essentials then presumably there would be a load balancer in front of the cluster handling incoming connections.  That device/software would also need its timeout extended as it would be waiting for the cluster to respond.

   

  As a best practice we do not recommend increasing the timeout beyond 60 seconds.  If your requests are exceeding 60 seconds, it is best to try to reduce the request time rather than increase the timeout, as shorter request times will scale much better.  Consider finding asyncronous methods or simplifying your requirements if possible!

   

  Regards,

   

  -Malcolm

  0

Please sign in to leave a comment.