Performance Issue On Oracle OAM Server Due To Audit.db
(Doc ID 2429134.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Platform Security for Java - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Oracle Access Manager 12c (OAM 18.104.22.168.0) WLS Managed server (oam_server1) Getting Struck Threads When Running a Security Scan
Having Performance issue and stuck thread on one of the Production OAM Servers the web page URl Load with 20 second delay, disabling the audit.db will resolve the issue. After disabling the <serviceInstanceRef ref="audit.db"/> from jps-config.xml the performance for OAM and struck thread got resolved.
But do not want to disable the audit.db and want to know why the performance is degraded for OAM due to audit.db. And customer is looking for fix for the issue causing by audit.db. Here customer is using security scan which is causing stuck thread whenever the security scan is running. But the performance issue is happening when the security scan is not running.
Requirement: Only OAM EVENTS to be audited (No need OPSS EVENTS)
1. Run DHS security scans
2. Access protected resource
3. Stuck threads show up after few hours
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