Skip to content

Refactor WebClientIntegrationTest to accommodate ReactorClientHttpRequest channel disassociation #33909

Closed
@bclozel

Description

@bclozel

As noticed by Simon, there might be issues with the way we associate our Reactor request support with the Reactor channel vs. Netty channel. This might be the reason some WebClientIntegrationTests are flaky.

After further investigation, this is due to the fact that the Channel is overwritten with a static one after the processing of the request to avoid usage of an outdated pooled connection/channel (see reactor/reactor-netty#3459).

This is a test issue, and we should capture something else than the native request. Perhaps the Attribute or the Channel.

Metadata

Metadata

Assignees

Labels

in: webIssues in web modules (web, webmvc, webflux, websocket)type: taskA general task

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions