Bug 1105160 – [GSS] (6.3.x) High CPU in concurrent access to the JSSESupport keySizeCache map

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1105160 - [GSS] (6.3.x) High CPU in concurrent access to the JSSESupport keySizeCache map

Summary:	[GSS] (6.3.x) High CPU in concurrent access to the JSSESupport keySizeCache map

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Web (Show other bugs)
Sub Component:
Version:	6.2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	ER9
Target Release:	EAP 6.3.0
Assigned To:	Aaron Ogburn
QA Contact:	Michal Karm Babacek
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:	1104206
Blocks:
	Show dependency tree / graph

Reported:	2014-06-05 09:43 EDT by Aaron Ogburn
Modified:	2014-10-25 08:38 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	The keySizeCache in JSSESupport was not properly synchronized in previous releases of JBoss EAP 6. This meant concurrent access to the JSSESupport keySizeCache could result in high CPU hash map loops. In this release of the product, access to the keySizeCache in JSSESupport is now synchronized and concurrent access to the keySizeCache does not occur.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-08-06 10:36:17 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	JBWEB-300	Major	Open	High CPU in concurrent access to the JSSESupport keySizeCache map	2017-01-18 17:10 EST

Groups: None (edit)

Description Aaron Ogburn 2014-06-05 09:43:13 EDT

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 1 Aaron Ogburn 2014-06-05 09:44:19 EDT

Fixed by the JBossWeb 7.4.5 component upgrade

Comment 2 Michal Karm Babacek 2014-07-11 15:48:30 EDT

I'm not sure I managed to reproduce it reliably, but the cache size is synchronized properly in the code, accordingly to the upstream tomcat patch. Switching to VERIFIED.

Note You need to log in before you can comment on or make changes to this bug.