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
VERIFIED on 6.2.4.CP.CR1