Skip to content
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

The premature closure of a TCP connection, resulting in the error "Connection prematurely closed BEFORE response," affects another connection. #3249

Closed
FfffatAss opened this issue May 17, 2024 · 3 comments
Assignees
Labels
status/invalid We don't feel this issue is valid

Comments

@FfffatAss
Copy link

Gradle dependents

buildscript {
ext {
springBootVersion = "2.7.12"
repositoriesUrl = 'http://172.16.1.136:8081/nexus/content/groups/public/'
}
repositories {
maven {
allowInsecureProtocol = true
url "${repositoriesUrl}"
}
}
dependencies {
classpath("org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}")
}
}

ext {
set('springCloudVersion', "2021.0.8")
}

dependencies {
implementation "org.apache.commons:commons-lang3"
implementation 'org.springframework.cloud:spring-cloud-starter-gateway'
implementation 'com.alibaba:fastjson:1.2.83'
implementation 'org.springframework.boot:spring-boot-starter-webflux'
testImplementation 'org.springframework.boot:spring-boot-starter-test'
}

Netty Version

version

Logs
log

Packages

package

From the packet, it can be seen that at 15:22:12.639, I was communicating with the server on port 8005 using the client with port 56616. I also received a response. At 15:22:12.731, the server disconnected from port 56620. In the log (there is an 8-hour time difference between the log and the packets, but they occurred at the same time), an error message can be seen at 07:22:12.732, indicating "Connection prematurely closed BEFORE response" from the client with port 56620 to the server with port 8005. However, this error affected my communication using the client with port 56616 and the server with port 8005. My request resulted in an error. I would like to ask if there is a bug in this case. My guess is that when I was communicating with the server using the client with port 56616 and the server almost simultaneously closed the idle connection on port 56620, it caused the error in the connection with port 56616 as well. The two connections were not handled separately, resulting in some confusion.

@FfffatAss FfffatAss added status/need-triage A new issue that still need to be evaluated as a whole type/bug A general bug labels May 17, 2024
@violetagg
Copy link
Member

@FfffatAss Are you able to update your Spring/Reactor versions? Are you able to provide a reproducible example?

@violetagg violetagg removed the status/need-triage A new issue that still need to be evaluated as a whole label May 23, 2024
@violetagg violetagg self-assigned this May 23, 2024
@violetagg violetagg added the for/user-attention This issue needs user attention (feedback, rework, etc...) label May 23, 2024
Copy link

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Copy link

github-actions bot commented Jun 7, 2024

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2024
@violetagg violetagg added status/invalid We don't feel this issue is valid and removed type/bug A general bug for/user-attention This issue needs user attention (feedback, rework, etc...) status/need-feedback labels Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/invalid We don't feel this issue is valid
Projects
None yet
Development

No branches or pull requests

2 participants