Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-1664

http/2 canceled requests cause UT005085: Connection was not closed cleanly, forcibly closing connection

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.2.0.Final
    • 2.0.29.Final
    • None
    • None
    • Hide

      https://github.com/carterkozak/http2-reproducer-undertow/tree/master/src/main/java/net/ckozak/repro/two

      1. Run Server.java main
      2. Run Client.java main

      wait a few moments (depending on hardware the timeouts may need to be modified). I've successfully reproduced on a linux workstation and macbook pro.

      This reproducer catches several types of issues, I've already filed issues and pushed fixes for several of them.

      Show
      https://github.com/carterkozak/http2-reproducer-undertow/tree/master/src/main/java/net/ckozak/repro/two 1. Run Server.java main 2. Run Client.java main wait a few moments (depending on hardware the timeouts may need to be modified). I've successfully reproduced on a linux workstation and macbook pro. This reproducer catches several types of issues, I've already filed issues and pushed fixes for several of them.

    Description

      This occurs intermittently using this reproducer: https://github.com/carterkozak/http2-reproducer-undertow/tree/master/src/main/java/net/ckozak/repro/two

      [XNIO-1 task-97] ERROR io.undertow - UT005085: Connection io.undertow.server.protocol.http2.Http2ServerConnection@5efe40bb for exchange HttpServerExchange{ POST /simple/ping} was not closed cleanly, forcibly closing connection

      Both invocations of this log message occur in a block annotated '//defensive programming, should never happen'

      Attachments

        Issue Links

          causes

          Task - Represents a small unit of work that is not end-user facing. UNDERTOW-2063 Review fix for UT005085, it is causing RST messages to be sent to client sometimes

          • 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.
          • Resolved
          relates to

          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) UNDERTOW-1700 Prevent resource leaks when Exchanges arent closed cleanly

          • 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.
          • Resolved

          Activity

            People

              flaviarnn Flavia Rainone
              carterkozak Carter Kozak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: