Bug 1103018

Summary: [GSS] (6.2.x) High CPU in concurrent access to the JSSESupport keySizeCache map
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Aaron Ogburn <aogburn>
Component: WebAssignee: Aaron Ogburn <aogburn>
Status: CLOSED CURRENTRELEASE QA Contact: Radim Hatlapatka <rhatlapa>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.1, 6.2.2, 6.2.3CC: bmaxwell, cdewolf, mhasko, smumford, vtunka
Target Milestone: CR1   
Target Release: EAP 6.2.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In previous versions of JBoss EAP 6, the `keySizeCache` in JSSESupport was not properly synchronized. Because of this, concurrent access to the JSSESupport keySizeCache could result in high CPU hash map loops. In this release, access to the keySizeCache in JSSESupport is synchronized and oncurrent access to the keySizeCache does not occur and high CPU hash map loops are avoided.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-07 12:12:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1067534, 1103019, 1103808    

Description Aaron Ogburn 2014-05-30 04:22:54 UTC 
The keySizeCache map in JSSESupport isn't protected from concurrent access and so can cause high CPU loops. The complete fix from the tomcat bug that had this map access synchronized wasn't used:

https://issues.apache.org/bugzilla/show_bug.cgi?id=47744
Comment 5 Michal Haško 2014-06-23 16:01:09 UTC 
VERIFIED on 6.2.4.CP.CR1