[jboss-jira] [JBoss JIRA] (WFWIP-155) WildFly gets stuck with TLSv1.3 on JDK 11

[Jan Stourac (Jira)]

     [ https://issues.jboss.org/browse/WFWIP-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Stourac resolved WFWIP-155.
-------------------------------
    Resolution: Done


I have tried this with build based on:
* https://github.com/fjuma/wildfly-elytron/tree/ELY-1706
* https://github.com/fjuma/wildfly-core/tree/WFCORE-4172
** rebased against current WildFly-Core master 245593b472abf284bbeefb4f46c7170b7651e65d
** XNIO 3.7.1.Final utilized
** Undertow 2.0.20.Final utilized
* WildFly branch used - current master 2ee5a9937eda7bd39878df9e5dad1181fb57ab2e, with aforementioned wildfly-core build.

I can see WildFly to no more stuck with TLSv1.3 following 'steps to reproduce'. Resolving this. [~adamkrajcik], raise your voice if you have any objections.

> WildFly gets stuck with TLSv1.3 on JDK 11
> -----------------------------------------
>
>                 Key: WFWIP-155
>                 URL: https://issues.jboss.org/browse/WFWIP-155
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Security
>         Environment: JDK 11
>            Reporter: Adam Krajcik
>            Assignee: Farah Juma
>            Priority: Blocker
>              Labels: jdk11
>
> WildFly gets stuck with when using TLSv1.3. The process starts to heavily use the processor and cannot be stopped by simple SIGINT(Ctrl+C).  The issue needs further investigation as no apparent reason for it being stuck.
> One possibility is mentioned in the comments for UNDERTOW-1493 is [JDK-8208526|https://bugs.openjdk.java.net/browse/JDK-8208526].



--
This message was sent by Atlassian Jira
(v7.12.1#712002)