The maximum number of sessions issue - iRAM
In iRAM application, our users encounters "The maximum number of sessions for this user has been reached. Log out from existing sessions or ask the system administrator to increase the maximum number of sessions per user."
We are able to reproduce this issue occasionally, however we do not know at what point of time, the issue occurs.
Seems this happened in less than 2 hours of normal operations on iRAM, by the user.
The abrupt increase in session is undesired and we do not know if this is really an HTTP session issue or Cache issue.
To help us investigate further, can we know if RAM development, enforce SESSION out (after what period of inactivity)?
We are able to reproduce this issue occasionally, however we do not know at what point of time, the issue occurs.
Seems this happened in less than 2 hours of normal operations on iRAM, by the user.
The abrupt increase in session is undesired and we do not know if this is really an HTTP session issue or Cache issue.
To help us investigate further, can we know if RAM development, enforce SESSION out (after what period of inactivity)?
2 answers
By default, RAM allows a maximum of 10 sessions per user. This limit exists to stop a single user from exhausting all of the server resources by creating multiple sessions. The maximum number of sessions per user may be changed on the RAM configuration page, see 'Maximum number of sessions per user:' user Performance Options.
Session timeout is configured and handled by your application server, not RAM. The default session timeout in WAS is 30 minutes.
The user may accidentally be creating multiple sessions in the web if they are using different browsers or cleaning their cookies.
Session timeout is configured and handled by your application server, not RAM. The default session timeout in WAS is 30 minutes.
The user may accidentally be creating multiple sessions in the web if they are using different browsers or cleaning their cookies.
Note that increasing the allowed sessions may temporarily fix a symptom but not solve the underlying problem: same uid connects to RAM again and again, creating a new session each time, not releasing their old session. ... increasing the number of allowed per user session will not help if the user is doing tens of requests.
Reason for the above, is a client (Web/API/Script...), connects to RAM without resending/reusing their session cookies.
Reason for the above, is a client (Web/API/Script...), connects to RAM without resending/reusing their session cookies.