Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-20313

(7.3.z) WFLY-13924 - HTTP2 is not working with Oracle JDK8 u261

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.3.5.GA, 7.3.5.CR1
    • 7.3.3.CR2, 7.3.2.GA
    • Security, Undertow
    • None
    • False
    • False
    • Hide
      Resolved with CUs JBEAP-20376 and JBEAP-20288
      Show
      Resolved with CUs JBEAP-20376 and JBEAP-20288
    • Hide

      Info about JDK used:

      $ /home/jstourac/jdks/jdk1.8.0_261/bin/java -version
java version "1.8.0_261"
Java(TM) SE Runtime Environment (build 1.8.0_261-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode)
      1. unzip the JBoss EAP
      2. start the server with proper JDK 
        JAVA_HOME=/home/jstourac/jdks/jdk1.8.0_261 ./jboss-eap-7.3.1/bin/standalone.sh
      3. wait till server boots up and perform an HTTP request (note that curl with HTTP2 support has to be used, otherwise use different client) 
        curl -k https://localhost:8443 -vvv >/dev/null
      4. see that HTTP/1.1 is used only; there is also this message in the output
        • ALPN, server did not agree to a protocol

      Now workaround:

      1. unzip the JBoss EAP
      2. start the server with proper JDK and property from UNDERTOW-1726 
        JAVA_HOME=/home/jstourac/jdks/jdk1.8.0_261 ./jboss-eap-7.3.1/bin/standalone.sh -Dio.undertow.protocols.alpn.jdk8
      3. wait till server boots up and perform an HTTP request 
        curl -k https://localhost:8443 -vvv >/dev/null
      4. see that HTTP/2 is used successfully now
      Show
      Info about JDK used: $ /home/jstourac/jdks/jdk1.8.0_261/bin/java -version java version "1.8.0_261" Java(TM) SE Runtime Environment (build 1.8.0_261-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode) unzip the JBoss EAP start the server with proper JDK JAVA_HOME=/home/jstourac/jdks/jdk1.8.0_261 ./jboss-eap-7.3.1/bin/standalone.sh wait till server boots up and perform an HTTP request (note that curl with HTTP2 support has to be used, otherwise use different client) curl -k https: //localhost:8443 -vvv >/dev/ null see that HTTP/1.1 is used only; there is also this message in the output ALPN, server did not agree to a protocol Now workaround: unzip the JBoss EAP start the server with proper JDK and property from UNDERTOW-1726 JAVA_HOME=/home/jstourac/jdks/jdk1.8.0_261 ./jboss-eap-7.3.1/bin/standalone.sh -Dio.undertow.protocols.alpn.jdk8 wait till server boots up and perform an HTTP request curl -k https: //localhost:8443 -vvv >/dev/ null see that HTTP/2 is used successfully now

    Description

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-20279 HTTP2 is not working with Oracle JDK8 u261

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFLY-13924 HTTP2 is not working with Oracle JDK8 u261

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-20288 [GSS] (7.3.z) Upgrade undertow from 2.0.32.SP1-redhat to 2.0.33.SP2-redhat

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-20376 (7.3.z) Upgrade WildFly Elytron from 1.10.9.Final-redhat-00001 to 1.10.10.Final-redhat

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-20390 (7.3.z) ELY-2026 - UnsupportedOperationException in SSLEngine using jdk 251+

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-20391 (7.3.z) UNDERTOW-1796 - Change the default value of the io.undertow.protocols.alpn.jdk8 to true

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-20392 (7.3.z) UNDERTOW-1800 - Change the order of the ALPN providers to prefer the JDK provider

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          links to

          Web Link KCS

          Activity

            People

              rhn-support-ivassile Ilia Vassilev
              istudens@redhat.com Ivo Studensky
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: