OAM Error when viewing Sessions Management
One can view the user session information from the OAM console. Meaning, you can view which users have accessed the applications which are being protected by OAM (Oracle Access Manager). This is a good feature for Administrators during troubleshooting any user access issues. The Sessions Management link/feature under OAM Launchpad (in 11gR2 PS2 the launchpad has been changed- Sessions Management link is available on the right handside). Click Sessions Management, new windows should open, where you can search via UserID. Search by " * " to view all the users who are currently accessing your environment - UserID, Creation time of session, Last Access Time info is clearly shown. This can be very helpful during troubleshooting user access issues.
Error while viewing sessions from Session Management from OAM console. Following errors were reported
Below error showed up on OAM console after clicking on Sessions Management
Error
Messages for this page are listed below
Checked other blogs and they were referring to possible issues with Coherence or other sub-systems.
Solution: Shutdown the OAM services for Admin and Managed and restarted them. The sessions were displayed fine via the OAM console with no error message. Note: for some reason the Admin server had to be restarted again.
Error while viewing sessions from Session Management from OAM console. Following errors were reported
Below error showed up on OAM console after clicking on Sessions Management
Error
Messages for this page are listed below
- Cannot instantiate the persistence access implemetation for class PersistedSessionCache
- Cannot get extractor list from passed configuration
- No storage-enabled nodes exist for service DistributedCache
Checked other blogs and they were referring to possible issues with Coherence or other sub-systems.
Solution: Shutdown the OAM services for Admin and Managed and restarted them. The sessions were displayed fine via the OAM console with no error message. Note: for some reason the Admin server had to be restarted again.
Comments
Post a Comment