Timeouts
- Optiva: \inetpub\wwwroot\FsOptivaWeb\Web.config file
Time-outs for Optiva are specified in the
Authentication
and
SessionState
sections of the
Web.config file. The authentication time-out forces
the user to log in again when the session has been idle. This protects the
application from usage by someone else.
The http timeout
setting
defines the number of seconds before the ASP.NET web service kills the currently running
process. This applies to the initial login, a long-running workflow script, or extensive
rollup, for example.
In the Web.config file in \FsOptivaWeb directory, specify the "timeout = "
values for closing down services not in use. The default value is
normally adequate; you can adjust the settings.
- The authentication time-out forces the user to log in
again when the session has been idle. This protects the application from usage
by someone else. The authentication time-out should be less than the
sessionState
time-out.<!-- AUTHENTICATION <authentication mode="Forms"> <forms name=".ASPXOPTIVAWEB" loginUrl="Login/ FsFrmLogin.aspx" timeout="120" /> </authentication>
- The
sessionState
protects the memory on the computer. If a specific session has not done anything for a period of time, then the information that is stored in the application is discarded; the user must log in again.<!-- SESSION STATE SETTINGS <sessionState mode="InProc" stateConnectionString= "tcpip=127.0.0.1:42424" sqlConnectionString="data source= 127.0.0.1;user id=sa;password=" cookieless="false" timeout="130" />
- A transaction time-out defines the number of seconds
before the ASP.NET web service kills the current process. This applies to the
initial login, a long-running workflow script, or extensive rollup, for
example.
This example specifies 48 hours for the time-out. This is appropriate for a long rollup.
<httpRuntime requestValidationType="FsOptivaWeb.CustomRequestValidator" executionTimeout="2600000" requestValidationMode="4.5" maxRequestLength="12096" useFullyQualifiedRedirectUrl="false" minFreeThreads="8" minLocalRequestFreeThreads="4" appRequestQueueLimit="100" />