03-11-2022 06:17 AM
So I was researching and found out that the Application Server recommends to set the Application Pools to not recycle at all. However, I know that there are quite a few things that require an application pool recycles. Can someone from Hyland explain why the MRG doesn't recommend having recycling at the application pool level setup? And if this is true, then what do you recommend us doing? Nightly full iisresets? iisresets with the /noforce switch? Something else?
Thanks.
03-21-2022 12:56 PM
Hi
The Application Server - OnBase Foundation EP5 Module Reference Guide on page 93 mentions
Reset Cache
Modules that use an Application Server do not reflect changes made in OnBase Configuration
until after the Application Server is refreshed. You can refresh the Application Server by
recycling its application pool or resetting its cache. For example, if you add a new print queue
or a print format, you need to refresh the Application Server in order for the changes to be
reflected in the Web Client. A refresh is not required for clients to reflect changes to user
privileges and rights, because these configurations are not cached.
Caution: Recycling the application pools disconnects users who are logged on to OnBase
through the Application Server or Web Server. Any unsaved work by these users will be lost.
Application pool recycling should occur during scheduled maintenance hours when no users
are connected to the Application Server.
You will see more details in Implementing Changes in Core Services starting on page 183 in the System Administration - OnBase Foundation EP5 Module Reference Guide.
Therefore, recycling your application pool only needs to be performed when large-scale changes, such as Application Server changes, are made. For these changes, you should schedule system downtime to recycle the application pool to ensure no users are connected to OnBase to prevent data loss.
Thanks!
~Alan
03-22-2022 04:11 PM
hi Ryan,
The Application Server MRG is referring to not recycle based on:
Depending on Windows Server version the default recycle value may be set to 1740 minutes, so at some point in the middle of the business day. This is why the MRG states to set it to 0.
If you want to do daily recycles, use the Specific time(s) option configured to an acceptable value for downtime. I don't see an option for a once a week recycle, though I could be missing the option.
Application Servers also need enough time to cleanup temporary data and active sessions. This could take 90 seconds or more. You may need to adjust the timeout on the application pool to allow the process to shutdown cleanly without the process from being killed.
IISReset can be used on a nightly or weekly schedule. It is going to stop all active Application Pools and the related IIS processes, so this is a longer process requiring a longer maintenance window. IISReset may be necessary when IIS gets into an unhealthy state where recycling an application pool does not resolve an issue. The timeouts described above also apply to this option.
hope this helps,
Doug
03-21-2022 12:56 PM
Hi
The Application Server - OnBase Foundation EP5 Module Reference Guide on page 93 mentions
Reset Cache
Modules that use an Application Server do not reflect changes made in OnBase Configuration
until after the Application Server is refreshed. You can refresh the Application Server by
recycling its application pool or resetting its cache. For example, if you add a new print queue
or a print format, you need to refresh the Application Server in order for the changes to be
reflected in the Web Client. A refresh is not required for clients to reflect changes to user
privileges and rights, because these configurations are not cached.
Caution: Recycling the application pools disconnects users who are logged on to OnBase
through the Application Server or Web Server. Any unsaved work by these users will be lost.
Application pool recycling should occur during scheduled maintenance hours when no users
are connected to the Application Server.
You will see more details in Implementing Changes in Core Services starting on page 183 in the System Administration - OnBase Foundation EP5 Module Reference Guide.
Therefore, recycling your application pool only needs to be performed when large-scale changes, such as Application Server changes, are made. For these changes, you should schedule system downtime to recycle the application pool to ensure no users are connected to OnBase to prevent data loss.
Thanks!
~Alan
03-22-2022 11:46 AM
We have a weekly maintenance window and app server / web server are recycled at that time. This has been helpful in purging old sessions since many folks are still working remotely and not restarting their PC on a regular basis. As stated, this will kick people out so make sure it's at a time of least activity.
03-22-2022 04:11 PM
hi Ryan,
The Application Server MRG is referring to not recycle based on:
Depending on Windows Server version the default recycle value may be set to 1740 minutes, so at some point in the middle of the business day. This is why the MRG states to set it to 0.
If you want to do daily recycles, use the Specific time(s) option configured to an acceptable value for downtime. I don't see an option for a once a week recycle, though I could be missing the option.
Application Servers also need enough time to cleanup temporary data and active sessions. This could take 90 seconds or more. You may need to adjust the timeout on the application pool to allow the process to shutdown cleanly without the process from being killed.
IISReset can be used on a nightly or weekly schedule. It is going to stop all active Application Pools and the related IIS processes, so this is a longer process requiring a longer maintenance window. IISReset may be necessary when IIS gets into an unhealthy state where recycling an application pool does not resolve an issue. The timeouts described above also apply to this option.
hope this helps,
Doug
03-22-2022 04:51 PM
Yes, this does help as well. This is all better descriptions and reasoning for why the MRG's really need to have 2 versions. A version for your generic users, and then another more granular detailed one for us techy techy people deep into the weeds. Lol
Thanks as always Doug. 🙂
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.