10 Aug 2012
20 Feb 2014
Link to this post
We've been upgrading our 5.0 websites to 6.3 over the last several weeks and we are noticing one issue that is a little concerning. Per the documentations recommendation, the application pools that run our Sitefinity sites are recycled nightly. We do this at 4:00am est. After this occurs, all of our 6.3 sites receive a Request Time out error for the first couple of minutes after this occurs. Our 5.0 sites do not have this issue. We also have service hit our homepage every two minutes so the site never spins down until we do the scheduled recycle, but still the pages that are not hit by the service get timeouts until they are hit. In addition, we use Xenu's Link Sleuth as a link checker and we have noticed that over half the site will return timeouts on underlying pages but if we go to those pages they display just fine. We end up having to run the link checker multiple times before all of the timeouts go away. Our goal is to have the site up at all times so having these timeouts occur at all isn't something we want to see. Our 5.0 sites do not have this timeout issue on Xenu's Link Sleuth at all.
I know there has been a lot of changes since 5.0 to 6.3 and we are already getting good results as far users talking about performance but we'd like an answer as to why this is happening and if there is a setting in Sitefinity we can change to fix this.