You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the sample provided there https://github.com/EtienneMiret/reactor-netty-oom the server closes connections at random points with socket.setSoLinger (true, 0). Meanwhile the client delays the start of reading with:
So in some cases FluxReceive#onInboundError is called before a subscription and when inboundDone is already true, which simply exits because it expects the cancellation or the completion to have done it.
The text was updated successfully, but these errors were encountered:
There are two use cases for HttpClient:
- a channelInactive is received, the response was fully received but there is no subscriber
- a error is receive while receiving the response and there is no subscriber
There are two use cases for HttpClient:
- a channelInactive is received, the response was fully received but there is no subscriber
- a error is receive while receiving the response and there is no subscriber
We cannot clean the queue with inbound data because we have use cases where the subscription is delayed. If we clean the queue such subscribers will not be able to consume the data.
Originally reported in spring-projects/spring-framework#25216.
In the sample provided there https://github.com/EtienneMiret/reactor-netty-oom the server closes connections at random points with
socket.setSoLinger (true, 0)
. Meanwhile the client delays the start of reading with:So in some cases
FluxReceive#onInboundError
is called before a subscription and wheninboundDone
is already true, which simply exits because it expects the cancellation or the completion to have done it.The text was updated successfully, but these errors were encountered: