We dont find any issue in non Prod but in PROD we see the issue in some cases.
We have a requirement not to allow multiple logins with same user.
When user already logged in, we add an entry into custom table and this entry would be removed when the user logged off or requestor is timed out. Agent runs for every 15 mins will check for pr_sys_context table and if entry is available in pr_sys_context table then that user record is cleared from custom table. If the entry available in custom table another session will not be logged in with the user.
But sometimes, even if the session timed out entry is not being added to pr_sys_context table which causes agent not able to pick the record so another session is not able to logged in.