ODSEE Directory Proxy Server 184.108.40.206.0 - High CPU and server hang is possible with CMS garbage collection.
(Doc ID 1554914.1)
Last updated on OCTOBER 14, 2019
Applies to:Oracle Directory Server Enterprise Edition - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1]
Information in this document applies to any platform.
After running normally for a period of time, DPS 22.214.171.124.0 consumes excessive CPU and may appear to be hung. Client requests are not processed. Garbage collection statistics from the JVM show a large number of full garbage collections and 100% utilization of old gen, similar to the following:
Note that the "O" column (old generation) shows 100% occupancy, even as the total number of full garbage collections (FGC) increases.
Verbose garbage collection logging may also show "concurrent mode failure" and/or "Promotion failure" messages.
JVM garbage collection was configured to use Concurrent Mark Sweep (CMS) with the JVM argument '-XX:+UseConcMarkSweepGC'.
This issue does not affect DPS with the default JVM configuration.
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