High CPU Usage with Stuck Thread at RoleAssignmentPolicyDecisionPoint
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.5 to 220.127.116.11
Information in this document applies to any platform.
High CPU usage occurs. Observations show that it is because stuck threads while managing the java.util.HashMap in the WebLogic Server (WLS) RoleAssignment and RoleMapper.
The HashMap seems corrupted due to the non-concurrent puts. The corrupted hashmap operations usually results in the high CPU. See the following dumped thread.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms