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:
-
The NT_TRANSACT_NOTIFY_CHANGE (section 2.2.7.4) subcommand
-
Read and write commands issued on an Open to a named pipe via the following commands:
-
TRANS_READ_NMPIPE (section 2.2.5.8 ) subcommand
-
TRANS_WRITE_NMPIPE (section 2.2.5.9 ) subcommand
-
TRANS_RAW_READ_NMPIPE (section 2.2.5.2 ) subcommand
-
TRANS_TRANSACT_NMPIPE (section 2.2.5.6 ) subcommand
-
TRANS_RAW_WRITE_NMPIPE (section 2.2.5.7 ) subcommand
-
TRANS_CALL_NMPIPE (section 2.2.5.11 ) subcommand
-
TRANS_WAIT_NMPIPE (section 2.2.5.10 ) subcommand
-
SMB_COM_LOCKING_ANDX Request (section 2.2.4.32.1 ) with the Timeout field set to a nonzero value
