The stale sessions are sessions that are incorrectly left in a running state after an agent or repository crash. If an agent crashes or loses its connection to the repository after it has started a session, the agent can’t update the status of the session in the repository, and such a session becomes stale. Until the stale session is cleaned, it displays as running in the repository, but actually is not.
The stale sessions are cleaned in multiple ways. The following are some examples:
-
You can manually request specific agents to clean stale sessions in Operator Navigator or Topology Navigator.
-
Stale sessions are cleaned when you restart an agent.
-
When an agent starts any new session, it checks for and resolves stale sessions. However, if the agent has lost connection to the repository, then it cannot clean stale sessions.