Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: 1.4.0.Beta1, 1.3.18.Final, 2.0.0.Alpha1
Affects Version/s: None
Component/s: Security
Labels:
None

Steps to Reproduce:
Hide

Configure HTTPS using TLS 1.2 for fips java (unsupported configuration)

Start eap (no error)

Access https://127.0.0.1:8443. Expected error java.security.NoSuchAlgorithmException: no such algorithm: SunTls12MasterSecret for provider SunPKCS11-testPkcs occures. EAP start to use 100% of CPU
Show
Configure HTTPS using TLS 1.2 for fips java (unsupported configuration) Start eap (no error) Access https://127.0.0.1:8443 . Expected error java.security.NoSuchAlgorithmException: no such algorithm: SunTls12MasterSecret for provider SunPKCS11-testPkcs occures. EAP start to use 100% of CPU

Description

100% CPU usage with unsupported configuration

Per [2] provided reproducer is not supported configuration and will be documented in [1]. My main concern here is if you can revise undertow implementation to avoid 100% CPU usage by any other SSL handshake error. See EAP thread dump and stack trace in attachment.

[1] https://issues.jboss.org/browse/JBEAP-3160
[2] https://bugs.openjdk.java.net/browse/JDK-8029661

Attachments

Issue Links

clones

JBEAP-3413 Check SSL/TLS handshake error handling in undertow

Closed

Activity

People

Assignee:: Stuart Douglas

Reporter:: Stuart Douglas

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2016/02/15 5:09 PM

Updated:: 2016/02/19 1:35 AM

Resolved:: 2016/02/15 5:20 PM