As explained in chapter User session expiration the Application Server implements a logic that automatically closes idle or abandoned sessions whenever a new user session is created. User sessions considered as active are never closed by the Application Server. Therefore global settings User sessions & security: Default User session timeout [s] and User sessions & security: Maximum allowed user session timeout [s] will influence if new user sessions can be created especially when you have many users and a low limit for allowed concurrent connections.

If the idling threshold for user sessions is high the Application Server the user sessions will be considered as active even if the user did not actively request data from the Application Server for a long time.