You are viewing limited content. For full access, please sign in.

Question

Question

idle timeout in IIS for all Laserfiche apps

asked on November 15, 2017

Is there any downside to setting the Idle Timeout to 0 in IIS for all Laserfiche web apps?

This prevents the awkward blank loading page that just confuses users since it feels more like no response then a loading page.

From my research, it's a setting to free up server memory, which seems pointless. If we have a properly configured Web Server, there will be enough memory allocated for all the apps at all times. I can't see how freeing up memory that is already free is worth the awkwardness.

0 0

Replies

replied on November 15, 2017

I'm not familiar with the blank loading page that you are referring to, so I can't comment on that part of the trade-off.  On the other side, for a product like Web Access, if the user does not explicitly log out of the repository then the connection to LFS will remain alive until the session expires.  This could cause problems if they reach the limit.

0 0
replied on November 15, 2017

After 20 minutes, the web application shuts down. It then takes 10 seconds or so to re-compile and load into memory. During this time the browser just displays a blank white page, making it appear that the app is not responding or unstable. You can reproduce by simply re-starting any web server and being the first to visit the site.

https://msdn.microsoft.com/en-us/library/ms366723.aspx

1 0
replied on November 16, 2017

Setting the application pool timeout to 0 should be fine, this is what the Laserfiche web client does starting with 10.3. I think Brian is referring to the session timeout, which should definitely be nonzero.

The application pool timeout is configured in the advanced settings for WebAccessAppPool, the session timeout is configured in the "Session State" section of the "Laserfiche" site.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.