Share via

3.2.3.6.1 Idle Scavenger Timer Expiry

  • Article

When the Idle Scavenger Timer expires, the server MUST scan all activities and remove idle calls and activities. After processing the following rules, the idle scavenger timer is reset to an implementation-specific interval.<94>

See product behavior note <95>for additional information.

Idle Call Processing: For each call in the Table of Active Calls per Activity, the server examines the Last Fragment Received timestamp value and compares it with the current time. If the interval is longer than an implementation specific value <96>, the call is determined to be idle and is removed from the Table of Active Calls per Activity.

Idle Activity Processing: For each activity in the Table of Activity IDs, the server examines the activities Last Use Timestamp and compares it with the current time. If the interval is longer than a period of TIMEOUT_IDLE as specified in [C706] Section 10.2.6, the activity is determined to be idle and is deleted from the Table of Activity IDs.

When an activity is deleted, the server MUST perform the following:

  • Delete all security contexts associated with the activity's Table of Security Contexts.

  • Using the activity's CAS UUID, lookup the appropriate CAS in the Table of Client Address Spaces, delete the Client Address Space and its CAS Context Handle List.