How to Control Application Pool Recycling in GEOVIA InSite

By

If you manage the GEOVIA InSite Application Server, particularly if you are working on the IIS Application Pool Recycling configurations, then this tip is for you. As part of the InSite server installation, GEOVIA consultants would have installed Web Platform on your site’s server machine, if not already performed by your local IT department.

However, the default IIS settings within the Application Pool Recycling may require some adjustments to work with other applications (in our case, the InSite web application). If there is a need to minimize the number of Recycles that occur (depends on your environment and traffic flow onsite – these are recommended guidelines for an optimal environment), please follow the below checklist and best practices.

First, open the Advanced Settings window by going to Start > IIS > Application Pools > InSite4AppPool.

On the Actions pane, click on Advanced Settings > Edit Application Pool section (see below image)

  • Application Pool Idle Timeout – The default setting is 20 minutes, so if the application does not get receive a request in 20 minutes then the App Pool will become idle and may take some time to start up again.
    The suggestion is to change this area to 0.The Idle Timeout should be set to 0 unless you are doing bulk hosting where you want to keep the memory footprint per site as low as possible. If there are only a few sites in a server and the aim is to get them to always load fast then set this to zero. Otherwise, as mentioned above, should 20 minutes pass without any traffic, the app pool will terminate and it can start up again on the next visit.
  • Regular Time Interval – The default is 1740 minutes; every 29 hours the App Pool will recycle, regardless of activity. Typically this is not desired, please set this to 0.
  • Specific Times – Normally by default, no schedule is set. Our recommendation is to set an off-peak time to recycle such as 4:00 AM.
  • IISReset – Importantly, please avoid using IISReset. Though it is a very powerful command that many users have used since IIS 5, it can have the potential to destabilize the operating environment. Unless you are installing ISAPI Filters or other System level change, there is no need to invoke IISReset.We recommend recycling the App Pool (in our case InSite4AppPool) when required, particularly after any changes to default settings, as opposed to IISReset.While IISReset will restart the whole web server, App Pool recycle will start a new instance of itself on a new thread and leave the old one to finish any work it is doing before shutting down.

Here are some examples when we may need to use App Pool recycling:

  • InSite DCS service is stuck processing a batch
  • InSite site security has been changed but not applied to web interface
  • New master data available in InSite and not syncing in Data Entry;
  • Page is unresponsive and refreshing it does help
  • Integration adaptor in loop (hanging, probably because the DCS service is stuck)

Note that if you have a heavy traffic site, you should use a long recycle schedule. If you have a low traffic site, use the shorter/default schedule to save memory.

For more GEOVIA InSite tips, you may be interested in Dashboarding & KPIs or Locking Data Via Account Period.

 

 

0
Mariana Nobile

Mariana Nobile

Technical Customer Support Consultant Mining, GEOVIA at Dassault Systèmes
Mariana Nobile has over 10 years’ experience in the mining industry, specifically providing technical software support to a range of customers, managing change deliveries, and assessing and testing pre-release products and improvements. Mariana is a subject matter expert for GEOVIA InSite, a production management tool. Based in Brisbane, Australia, she is fluent in English, Spanish and Portuguese.