Troubleshooting
Problem
High CPU or hang symptoms may be observed on java.util.HashMap.findNonNullKeyEntry when a HashMap is utilized in a non-thread-safe manner. This is an unsafe coding practice that can occur at any level of development when using the HashMap API: application, application server, third party module, etc. The following will outline how to identify the problematic code and some possible methods to resolve the issue.
Symptom
High CPU or hung threads with an executing stack similar to the following:
at java.util.HashMap.findNonNullKeyEntry()
at java.util.HashMap.getEntry()
at java.util.HashMap.get()
at com.xyz.methodABC()
...
- at java.util.HashMap.findNonNullKeyEntry()
at java.util.HashMap.putImpl()
at java.util.HashMap.put()
at com.xyz.methodABC()
...
The specific stack may vary.
As a more general symptom of this issue, the executing stack will show the problematic code calling a method within the HashMap API which will in turn call the findNonNullKeyEntry() method.
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21597581