https://bz.apache.org/bugzilla/show_bug.cgi?id=66476
Bug ID: 66476 Summary: org.apache.tomcat.util.net.Acceptor.run Socket accept failed java.io.IOException: Duplicate accept detected. Product: Tomcat 9 Version: 9.0.58 Hardware: PC OS: Linux Status: NEW Severity: critical Priority: P2 Component: Connectors Assignee: dev@tomcat.apache.org Reporter: patkarom...@gmail.com Target Milestone: ----- Hello, Sometimes we see below error in our tomcat log file, and when this happens tomcat stops accepting any more requests : - ---------------------------------- ERROR: - ---------------------------------- 10-Feb-2023 02:16:19.618 SEVERE [http-nio-80-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) ---------------------------------- Apache Tomcat version : - Apache Tomcat/9.0.58 Frequency of occurance : - Sometimes Reproducible consistently ? : - No, it appears sometimes ....randomly...and on tomcat restart it goes away but it may appear randomly sometime later OS = CentOS Kernel (uname -sr) = Linux 6.0.9-1.el7.elrepo.x86_64 Server arch = amd64 Setup: - We are using Camunda 7.16 BPMN tool which comes with inbuilt Apache Tomcat 9.0.58. This is deployed on our Linux VM (CentOS). The VM is within our company network, and ... via company's firewall another trusted application on Azure cloud (outside company network)...is only allowed to make REST API calls to Camunda (hosted on Tomcat). When Tomcat is started all works fine, requests placed from trusted application on Azure Cloud are able to reach our Tomcat and our application works on it, until out of the blue and randomly above error occurs and tomcat no longer serves request coming from external application on cloud. On the other hand, if we fire similar request from within our company network machines as many times as we want... as frequently as possible, in such scenario, the above error does not occur and Tomcat allows all requests. In other words, it seems above issue occurs only for external requests and not internal ones. What has been tried so far ?: - >From several posts after google search it was found that Linux Kernel version could help. Previously it was 3.x and now it is upgraded to 6.0.9-1 and Apache Tomcat version is 9.0.58... still we face the above error. Queries: - 1) Why it behaves strangely with external requests and not with internal ones ? 2) How can we consistently reproduce the issue ? 3) What could be the possible cause and how to fix it ? Any help in this regard can be very helpful. Let me know if you need any more information. Thanks and Regards Omkar Patkar -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org