-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.6 Larks
-
Fix Version/s: 2.7 Larks
-
Labels:None
-
Sprint:2.7 Larks
It looks like when we're under a load, we don't close sockets and we run out of system resources:
Mar 23, 2014 6:04:19 AM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
SEVERE: Socket accept failed
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
at java.net.ServerSocket.implAccept(ServerSocket.java:530)
at java.net.ServerSocket.accept(ServerSocket.java:498)
at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:352)
at java.lang.Thread.run(Thread.java:724)
I assume that there are bots that open connections and don't close them properly, but that's just an assumption.
There might be Tomcat configuration options that prevent this behaviour.
- Testing discovered
-
-
- Closed
-
1.
|
Reproduce socket leakage in JC |
|
Closed | Vladislav |