New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SLEngine closed already #1828
Comments
@AlexieKA Is the connection closed at some point or it stays always opened? |
The connection is closed later and the errors end. |
@violetagg Hi, I have a question about this.
I just configured SO_KEEPALIVE and I faced below logs.
|
We have the same issue:
|
@hamadodene Your issue is not the same because it happens on the server. |
Hi, |
@leejegirl We will try for 1.0.17 but most probably 1.0.18. If somebody wants to provide a PR with the fix, I'll be able to review it. |
@violetagg |
@violetagg, I have a question.
|
@leejegirl It is described here https://projectreactor.io/docs/netty/release/reference/index.html#_connection_pool_2
|
@violetagg Are they right?
and
And I have two more questions.
|
Im being confused by sample of https://projectreactor.io/docs/netty/release/reference/index.html#_connection_pool_2 |
@leejegirl How can we improve the documentation so that it is less confusing? |
yep
yep
Please tell me the concrete use case that you have for
yep |
I suggest to be added the sample for multi http request because I confused that I need to make HttpClient and create WebClient instance for each http request or not. |
@leejegirl Do you want to provide a PR? |
No, I don't ^^ |
|
Show that with one and the same HttpClient instance, one can initiate many requests that always will use a new connection. Related to comment #1828 (comment)
@leejegirl I prepared a PR #2082 for extending the documentation with your suggestion. Please take a look. |
Show that with one and the same HttpClient instance, one can initiate many requests that always will use a new connection. Related to comment #1828 (comment)
@violetagg It's better. Thanks. |
Our application is sending a large number of messages in parallel over HTTPS. Below is the HTTP client creation code (kotlin):
Source code for sending:
We faced with a floating-issue that mainly occurs with high load:
Extended logs for the problem channel below (real IP and URL are replaced):
In my opinion, the following situation occurs:
Expected Behavior
The channel is not acquired if the session is closed.
Actual Behavior
The channel is acquired (many times) for closed session.
Steps to Reproduce
Possible Solution
Disable connection pool:
var httpClient = ReactorHttpClient.newConnection()
Your Environment
org.springframework.boot:spring-boot-starter-reactor-netty:2.5.4
| | --- io.projectreactor.netty:reactor-netty-http:1.0.10
| | +--- io.netty:netty-codec-http:4.1.66.Final -> 4.1.67.Final
| | +--- io.netty:netty-codec-http2:4.1.66.Final -> 4.1.67.Final
| | +--- io.netty:netty-resolver-dns:4.1.66.Final -> 4.1.67.Final
| | +--- io.netty:netty-resolver-dns-native-macos:4.1.66.Final -> 4.1.67.Final
| | +--- io.netty:netty-transport-native-epoll:4.1.66.Final -> 4.1.67.Final
| | +--- io.projectreactor.netty:reactor-netty-core:1.0.10
| | --- io.projectreactor:reactor-core:3.4.9 (*)
java -version
): java11-runtime-11.0.10+9The text was updated successfully, but these errors were encountered: