Closing of a session can be triggered by several different events. As soon as a session is closed any requests to the Application Server with the session token of the closed session will fail. Whenever a session is closed the system writes the Session end date to the session. Note that this Session end date does not necessarily mean that the user who initiated that session stopped working at that point in time.
The session closing trigger will be remembered in the user session log.
Session closing trigger |
Notes |
User's request |
If the user intentionally logs out from the Application Server and therefore closes his own session |
Forcefully closed |
A user with the system permission Close user sessions (3) closed the sessions of another user. |
System start up |
On start up of the Application Server all sessions still marked as open are closed with this state. While usually all open sessions are closed on shutdown of the Application Server there might still be open sessions on start up if the server could not finalize all shutdown actions cleanly. |
System shut down |
On shutdown of the Application Sever all open session are closed with this stat. |
Idling |
When a new user session shall be created but the license does not allow any more concurrent connection, the Application Server automatically closes the session that has bee idling for the longest time. |
Abandoned |
Before creation of a new user session all abandoned user sessions are closed with this state. |
Server update |
When the server performs a data update all open sessions of users who do not have the system permission Create user session when server is closed (13) will be closed with this state. |
Table 1: Events that trigger the closing of sessions
