QAID # 13973 Published
Question / Problem:
Why might the Kofax Transformation Modules Thin Client time out other than after a normal period of inactivity, and what might this have to do with IIS worker process recycling?
Answer / Solution:
Timeouts are a normal part of any session-based Web application. Please see QAID 13529 for information about how to configure the length of the timeout.
Aside from normal timeouts caused by periods of inactivity, a timeout message can also be triggered by IIS recycling the worker process. There are several settings that do this that are configured on the Recycling tab of the Application Pool's properties in IIS. When any of the settings on this tab are triggered, logged-in users will be timed out and their Batches will be suspended.
The default settings will restart the worker process after 1,740 minutes (29 hours) of inactivity. However this would not trigger unless the AppPool timeout is higher than this number, or disabled (see QAID 13529). And only if the web.config timeout was higher than that number would this ever cause Thin Client sessions to be closed.
If the other settings on this tab are customized and their conditions are met, or if the Application Pool is manually recycled, then Thin Client sessions will be lost and users will receive timeout messages.
|AXPRO||4.5||Thin Client Validation|
|AXPRO||5.0||Thin Client Validation|