There seems to be some problem with HTTP2 support with new Oracle JDK8 u261 and JBoss EAP since 7.3.2.GA version. When request against server is executed, then HTTP2 is not established and communication remains via HTTP/1.1.
There is no such issue when I use JBoss EAP 7.3.1.GA. Also, if I switch back to an older Oracle JDK8 u241, there is no such issue even with newer JBoss EAP versions. And also there is no issue when I use JBoss EAP 7.3.1.GA with Oracle JDK8 u261.
This all seems to be tied with backport of ALPN support into the Oracle JDK8 recently and also work in following issue UNDERTOW-1726.
There seems to be a workaround available - to define '-Dio.undertow.protocols.alpn.jdk8' during the server startup. With this property configured, the issue seems to disappear (as such, blocker priority of this may be discussed).
What is the issue here:
This is a change in default behavior of the server (HTTP2 not working with Oracle JDK8u261+ since JBoss EAP 7.3.2.GA). We should try to resolve this without default behavior change if possible. Only in case there is really no other solution, we need to document such thing. There is no note in our release notes for the 7.3.2 release. Just a reference to the JBEAP-19631 but with no actual explanation for its effect.
- clones
-
JBEAP-20279 HTTP2 is not working with Oracle JDK8 u261
- Closed
-
WFLY-13924 HTTP2 is not working with Oracle JDK8 u261
- Closed
- is incorporated by
-
JBEAP-20288 [GSS] (7.3.z) Upgrade undertow from 2.0.32.SP1-redhat to 2.0.33.SP2-redhat
- Closed
-
JBEAP-20376 (7.3.z) Upgrade WildFly Elytron from 1.10.9.Final-redhat-00001 to 1.10.10.Final-redhat
- Closed
- is related to
-
JBEAP-20390 (7.3.z) ELY-2026 - UnsupportedOperationException in SSLEngine using jdk 251+
- Closed
-
JBEAP-20391 (7.3.z) UNDERTOW-1796 - Change the default value of the io.undertow.protocols.alpn.jdk8 to true
- Closed
-
JBEAP-20392 (7.3.z) UNDERTOW-1800 - Change the order of the ALPN providers to prefer the JDK provider
- Closed
- links to