-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
8.2.0.Final
-
-
User Experience
I'm facing an issue similar to UNDERTOW-427. If the client doesn't read the entire response sent by the server and terminates the connection before server does, then there is socket leak.
Open files count
=============
[root@xyz apps]# lsof -p <jboss-pid> | wc -l
1331
[root@xyz apps]# lsof | wc -l
12049
After running around 1.5 k times.
=========================
[root@xyz apps]# lsof -p <jboss-pid> | grep "can't identify pro" | wc -l
1539
[root@xyz apps]# lsof -p <jboss-pid> | wc -l
2998
[root@xyz apps]# lsof | wc -l
14831
- is related to
-
WFLY-8466 Socket leak when setting HTTP Content-Length and client not reading entire response
- Closed