Skip to content

Server closes the connection with a FIN packet immediately after sending a GO_AWAY frame. All accepted streams upto the lastStreamId are not getting processed #2735

Closed
@Sumi264

Description

@Sumi264

My application server using http2 reactive netty server (version: 1.0.26) closes the connection immediately after sending a GO_AWAY packet, without processing outstanding requests up to the lastStreamId.

+--- org.springframework.boot:spring-boot-starter-webflux:2.7.7
| +--- org.springframework.boot:spring-boot-starter:2.7.7 ()
| +--- org.springframework.boot:spring-boot-starter-json:2.7.7 (
)
| +--- org.springframework.boot:spring-boot-starter-reactor-netty:2.7.7
| | --- io.projectreactor.netty:reactor-netty-http:1.0.26

https://www.rfc-editor.org/rfc/rfc7540#section-6.8 states that all "Activity on streams numbered lower or equal to the last stream identifier might still complete successfully. The sender of a GOAWAY frame might gracefully shut down a connection by sending a GOAWAY frame, maintaining the connection in an "open" state until all in-progress streams complete."

Does reactive netty server support processing of all accepted streams upto the lastStreamId sent in GO_AWAY frame before terminating the connection? If yes, then please advise if some configuration is needed to make reactive netty http2 server to ensure the processing of all streams up to the lastStreamId quoted in GO_AWAY frame.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions