High CPU Across All Nodes During EP Execution After Upgrading To 14c Feature Pack
(Doc ID 3021252.1)
Last updated on MAY 15, 2024
Applies to:
Oracle Coherence - Version 14.1.1.2206.7 and laterInformation in this document applies to any platform.
Symptoms
High CPU Across All Nodes During EP Execution After Upgrading To 14c Feature Pack.
The issue reported that during the copy of one particular cache, the CPU usage shoots to 100% across all the machines hosting the Coherence Cluster. Found that most of the CPU time was spent calling Arrays.toString. EntryProcessor code is supposed to just do a binary update and no serialization should be happening, so when it was inspected further found that it is actually an evaluation of an assertion error message, which is the null check in the com.tangosol.util.filter.ArrayFilter constructor. This Arrays.toString was not there before in our previous version of coherence.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |