High CPU in concurrent access to the JSSESupport keySizeCache map

Environment

• JBoss Enterprise Application Platform (EAP)
  • 6.2 CP01
  • 6.2 CP02
  • 6.2 CP03

Issue

• JBoss is consuming high CPU. Thread dumps and CPU data shows high CPU in web request threads that are accessing the keySizeCache WeakHashMap in JSSESupport.getKeySize().

Resolution

• Apply JBoss This content is not included.EAP 6.2 CP04
• Upgrade to EAP 6.3.0+

Root Cause

• Multiple request threads are checking SSL request attributes at once, allowing for concurrent access to the keySizeCache map, causing high CPU HashMap loops. Concurrent access to HashMaps causes loops per High CPU due to multiple Java threads accessing HashMap simultaneously
• Content from issues.jboss.org is not included.JBWEB-300
• This content is not included.BZ-1103018
• This content is not included.BZ-1105160

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.