Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 7.0.0.ER6
Affects Version/s: 7.0.0.ER5
Component/s: Security, Undertow
Labels:
None

Target Release:

7.0.0.GA
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

SFDC Cases Counter:
SFDC Cases Links:

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

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

eap.stacktrace
2 kB
2016/02/15 9:07 AM
fips_tls12.threaddump
54 kB
2016/02/15 9:07 AM
standalone.xml
22 kB
2016/02/15 9:07 AM

Issue Links

is cloned by

UNDERTOW-633 Check SSL/TLS handshake error handling in undertow

Resolved

Activity

People

Assignee:: Stuart Douglas

Reporter:: Martin Choma

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2016/02/15 9:08 AM

Updated:: 2021/10/24 5:42 AM

Resolved:: 2016/02/23 5:49 PM