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

Intermittent error with connection reset by peer. #3219

Closed
sokavidyasagar opened this issue May 2, 2024 · 3 comments
Closed

Intermittent error with connection reset by peer. #3219

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

Comments

@sokavidyasagar
Copy link

We are using microservice architecture(Spring Boot application deployed on AWS EKS) and we are getting "connection reset by peer" when trigger API call from my service to other application.

Expected Behavior

Successful handshake with other application we tried to connect

Actual Behavior

Intermittent issue with connection reset by peer issue.
recvAddress(..) failed: Connection reset by peer; nested exception is io.netty.channel.unix.Errors$NativeIoException: recvAddress(..) failed: Connection reset by peer org.springframework.web.reactive.function.client.WebClientRequestException: recvAddress(..) failed: Connection reset by peer; nested exception is io.netty.channel.unix.Errors$NativeIoException: recvAddress(..) failed: Connection reset by peer

Steps to Reproduce

unable reproduce

@Test
public void repoCase() {

}

Properties :
connection:
maxConnections: 500
maxIdleTime: 20
maxLifeTime: 60
pendingAcquireTimeout: 45
evictInBackground: 120

Possible Solution

Validate a connection before triggering API call.

Your Environment

We are using : io.projectreactor.netty:reactor-netty-http:jar:1.0.38
Java version: 1.8

  • Reactor version(s) used:
  • Other relevant libraries versions (eg. netty, ...):
  • JVM version (java -version):
  • OS and version (eg. uname -a):
@sokavidyasagar sokavidyasagar added status/need-triage A new issue that still need to be evaluated as a whole type/bug A general bug labels May 2, 2024
@violetagg violetagg self-assigned this May 5, 2024
@violetagg violetagg added for/user-attention This issue needs user attention (feedback, rework, etc...) and removed status/need-triage A new issue that still need to be evaluated as a whole labels May 5, 2024
@violetagg
Copy link
Member

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

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 May 20, 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 May 20, 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