3.2.6.1 Request Expiration Timer Event

When the Request Expiration Timer (section 3.2.2.1) expires, the client MUST walk the outstanding commands in Client.Connection.PIDMIDList for any pending commands that have exceeded Client.SessionTimeoutValue. If a command has exceeded Client.SessionTimeoutValue,<210> the client SHOULD<211> close the connection to the server, and all resources associated with the connection MUST be freed, as specified in section 3.2.7.1.

The NT_TRANSACT_NOTIFY_CHANGE (section 2.2.7.4) subcommand MUST be exempt.

The following commands are exempt from the Request Expiration Timer:

Show: