When you employ the persistent client session context functionality of ASOLib, client context sessions may be abandoned by the end user, wasting resources on the server machine. This can happen when a client exits or terminates without a clean shutdown (that is, omitting a call to DestroyASOSession). To protect against this, session timeout functionality is built into ASOLib. This housekeeping functionality is invoked periodically by the Server Manager monitoring tool. The timeout values are configurable by client type.

Each client type can have its own dormant limit. The dormant limit is the amount of time that a session context can remain unused before it is marked as a candidate for destruction. For more information about how this works and how to override the defaults, see uc_client_info Class (see uc_client_info Class).