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

SEVERE [https-jsse-nio-8443-Acceptor] org.apache.tomcat.util.net.Acceptor.run Socket accept failed #29073

Closed
Parashuraam opened this issue Sep 5, 2022 · 5 comments
Labels
status: duplicate A duplicate of another issue

Comments

@Parashuraam
Copy link

Parashuraam commented Sep 5, 2022

Hi Team,

  can someone help me with the below issue?

 OS Name:  Red Hat Enterprise Linux Server
 OS Version: 7.9 (Maipo)
 OS Kernel :  3.10.0-1160.76.1.el7.x86_64
 Tomcat Server version: Apache Tomcat/9.0.58
 Server version: Apache Tomcat/9.0.58
 Architecture:   amd64
 JVM Version:    1.8.0_221-b32
 JVM Vendor:     Oracle Corporation
 :: Spring Boot ::        (v2.1.2.RELEASE)

  **ERROR :**

  04-Sep-2022 13:05:47.165 SEVERE [https-jsse-nio-8443-Acceptor] org.apache.tomcat.util.net.Acceptor.run Socket accept failed
    java.io.IOException: Duplicate accept detected. This is a known OS bug. Please consider reporting that you are affected: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298
            at org.apache.tomcat.util.net.NioEndpoint.serverSocketAccept(NioEndpoint.java:548)
            at org.apache.tomcat.util.net.NioEndpoint.serverSocketAccept(NioEndpoint.java:78)
            at org.apache.tomcat.util.net.Acceptor.run(Acceptor.java:129)
            at java.lang.Thread.run(Thread.java:748)
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Sep 5, 2022
@bclozel
Copy link
Member

bclozel commented Sep 5, 2022

This is a duplicate of #26434, but related to Spring Framework. See Mark's comment for proper resolution.

@bclozel bclozel closed this as not planned Won't fix, can't repro, duplicate, stale Sep 5, 2022
@bclozel bclozel added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Sep 5, 2022
@Parashuraam
Copy link
Author

please can you tell me solution steps for it.

@bclozel
Copy link
Member

bclozel commented Sep 5, 2022

Please read the comment I've pointed to. This is related to an OS bug. Follow Mark's advice for resolution.

@btpnlsl
Copy link

btpnlsl commented Sep 6, 2022

@bclozel The OS bug in the Linux TCP/IP stack was fixed in version 5.10-rc6 of the Linux kernel and was backported to LTS versions of the kernel as well. I don't think it is helpful to continue to report this to Ubuntu as requested by Mark as they have already incorporated this bugfix into their LTS versions. The best solution now is to look for an OS version which incorporates the fix.

@Parashuraam You would need to update your OS (RedHat) and investigate to determine which versions of RedHat have incorporated the bugfix.

The bugfix you are looking for is this one: torvalds/linux@01770a1

@y0zg
Copy link

y0zg commented Sep 21, 2022

Does anyone know how to fix this on AWS EKS?
I see the latest kernel version in AMIs - 5.4 https://github.com/awslabs/amazon-eks-ami/blob/master/CHANGELOG.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

5 participants