Date: Thu, 28 Mar 2024 21:04:45 +0000 (UTC) Message-ID: <663517763.9817.1711659885809@catch-kbase-p> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_9816_222628809.1711659885808" ------=_Part_9816_222628809.1711659885808 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In some cases though the timeout in Enterprise Tester may be set= very high, but timeout's still occur much earlier than the configured time= out period - normally after approximately 20 minutes of idle time. This nor= mally affects IIS6 & IIS7, and is predominantly caused by the applicati= on pool "idle timeout" period due to Enterprise Tester's default usage of "= in-proc" state session storage.
There are a couple of approaches to resolving this problem:
Increasing the idle timeout for the application pool.
Configuring Enterprise Tester use "out of proc" session storage.
=The idle timeout determines the number of minutes the application pool (= and thus the application Enterprise Tester) will be held in memory, with an= y requests being made, before the application is automatically unloaded fro= m memory.
On most default IIS installations, this value will default to 20 minutes= .
In addition there is also another setting, which controls the maximum nu= mber of minutes the application pool can be active before it is recycled - = this setting is the "Regular Time Interval (minutes)" Recycle trigger. This= feature is intended to recycle the process on a regular basis (normally ev= ery 1-2 days) to avoid the effects of memory leaks etc. that may exist in s= oftware.
Go to Control -> Administrative Tools -> Internet Information = Services (IIS) Manager.
Expand the server node, you will see an "Application Pools" node.
Right click on the Application pool (it will normally be the "Defaul= t App Pool", but it may alternatively be called "Enterprise Tester") and se= lect Properties...
On the dialog, click on the Recycling tab - from here you can config= ure how long an application pool will be active before it's forced to recyc= le - this should be set to a value greater then 24 hours (i.e. 1440 minutes= ).
Switch to the "Performance tab".
Locate the "Shutdown work processes after being idle for (time in mi= nutes)" setting. You can either choose to uncheck the checkbox (disabling t= his all together) - or alternatively, set the value to be the same as (or h= igher) then the timeout value configured in Enterprise Tester.
Go to Control -> Administrative Tools -> Internet Information = Services (IIS) Manager.
Expand the server node, then select the "Application Pools" node.
Select the pool being used for Enterprise Tester (usually "DefaultAp= pPool") - though in some cases a specific "EnterpriseTester" pool may have = been created.
With the pool selected, on the right hand actions list select "Advan= ced Settings..."
Scroll down until you locate the "Process Model" section - here you = can configure the "Idle Time-out (minutes)" value, set the value to be the = same as (or higher) then the time-out value configured in Enterprise Tester= .
Scroll down until you locate the "Recycling" section, and configure = that the "Regular Time Interval (minutes)" is configured for a value greate= r then 24 hours (ie. 1440 minutes).
Included with the .NET SDK is a Windows=C2=AE NT service: ASPState. This= Windows service is what ASP.NET uses for out-of-process session state mana= gement. To use this state manager, you first need to start the service. To = start the service, open a command prompt and type:
net sta= rt aspstate
What you'll see is:
At this point, the Windows NT Service ASPState has started and is availa= ble to ASP.NET. Next, we need to configure ASP.NET to take advantage of thi= s service. To do this we need to update the web.config:
Locate the <system.web> section, then add this immediately beneath= it:
<sys= tem.web> <configuration> <sessionstate=20 mode=3D"stateserver" cookieless=3D"false"=20 server=3D"127.0.0.1"=20 port=3D"42424"=20 /> </configuration>
Then save the changes.
At this point the application should start using the state server for st= oring session information - this is a resilient store that will survive whe= n the application pool is recycled.
See this msdn article for = more details on in-proc and out-of-proc session state in ASP.Net.