RE: liferay 7.4 ga24 tomcat Socket accept failed exception

Scarletake Bwi, modified 3 Years ago. Expert Posts: 327 Join Date: 12/20/10 Recent Posts

 hi

i am using liferay 7.4 ga24 on windows server 2019 with jdk8. 

i have no idea why it happen, it just shows exceptoin as follows

01-Jul-2022 13:36:13.218 SEVERE [https-jsse-nio-443-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:545)
        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)

 my os is windows server, not ubuntu or linux. i do not know should i ignore it or not, becuse liferay still work and work fine.

 

is it coused by ssl setting? my server.xml

    <Connector port="80" protocol="HTTP/1.1"
               maxThreads="150" minSpareThreads="25" 
               enableLookups="false" redirectPort="8443" acceptCount="100"
               connectionTimeout="20000" disableUploadTimeout="true" />
 
    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" URIEncoding="UTF-8" secretRequired="false" />
 

<Connector port="443" maxThreads="150" scheme="https" 
   secure="true" SSLEnabled="true" 
   keystoreFile="C:\SSL\keystorep" 
   keystorePass="xxxxxxx" 
   clientAuth="false" 
   SSLProtocol="TLSv1.2"/>

thanks in advance

thumbnail
Olaf Kock, modified 3 Years ago. Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts

I'm not sure what it's caused by, or if it's something that requires attention.

I've just seen that the ubuntu ticket also has one comment that mentions this happening on Windows, from January this year.

You might want to check if updating your tomcat (either together with Liferay or without) fixes it.

Or you might be running in Docker - in that case you might well run in Ubuntu on Windows.