OAM Session Database Idle Sessions Are Not Purged: How To Check The Status Of The Session Reaper
(Doc ID 2204981.1)
Last updated on MARCH 30, 2021
Applies to:Oracle Access Manager - Version 188.8.131.52.5 and later
Information in this document applies to any platform.
OAM Session Database Idle Sessions Are Not Purged: How To Check The Status Of The Session Reaper?
The OAM database is still storing old OAM sessions that have long since been ended or timed out. The database would also contain multiple sessions per user. These examples can all be seen by either querying into the OAM sessions table or going into the OAM console and searching up specific users in OAM session search that will bring up multiple oam sessions from days or weeks back. However after testing it further it appears to be only affecting one OAM server and doesn't appear to be affecting the user side. Although OAM console may show that a user has a session that is supposed to be closed, it still asks them to log in as expected as if they didn't have an oam session. It appears the oam sessions that are being created are timed out/ended successfully however the database still displays that they are active when they are not. This issue is not seen for every single user however it appears that the database is filling up with the users that are affected having many multiple sessions.
How to check the status of the Session Reaper thread and clean up the piled up expired sessions directly from DB?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document