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.
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:
Fixed by the JBossWeb 7.4.5 component upgrade
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.