Skip to content

Http2Pool is exhausted after timeouts with HTTP 1.1 #3804

@vklidu

Description

@vklidu

If I configure the HTTP server to use only the HTTP 1.1 protocol and set the client to use both HTTP 1.1 and H2C, an error may occur. The client creates a connection pool called Http2Pool. If a timeout occurs during a request, the connection is closed but the stream is not released. In the debug log, you can then see a message like: "Channel is closed, 1 active streams." This connection still counts towards the number of connections in the pool, and over time, the entire pool gets exhausted. These connections are never released.

reactor-netty version: 1.2.6

Example can be found here: https://github.com/vklidu/reactor-netty-timeout

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions