Hi, thanks for this report. Some questions to help us help you— - What OS for client and server? - Are you seeing the sockets clean up over time or do they persist until a reboot? - Does netstat give you any additional information about the sockets? Are any in TIME_WAIT status? - Do you have a tcpdump of the socket? - What is the scenario? Is it “normal” operation or is the client or server killed? - Do you have a reproducible test case?
Thanks, Anthony > On Nov 16, 2021, at 9:28 AM, Leon Finker <leon...@gmail.com> wrote: > > Hi, > > We observe in our geode (1.14 - same before as well in 1.13) cache > server (that supports durable client sessions) an increase in half > opened sockets. It seems there is a socket leak. Could someone > recommend how to track the leak down? It's not obvious where it's > leaking...I can only suspect AcceptorImpl.run and where it only > handles IOException. but I wasn't able to reproduce it in debugger > yet... > > lsof -p 344|grep "can't" > > java 344 user 133u sock 0,6 0t0 115956017 > can't identify protocol > java 344 user 142u sock 0,6 0t0 113361870 > can't identify protocol > java 344 user 143u sock 0,6 0t0 111979650 > can't identify protocol > java 344 user 156u sock 0,6 0t0 117202529 > can't identify protocol > java 344 user 178u sock 0,6 0t0 113357568 > can't identify protocol > ... > > lsof -p 344|grep "can't"|wc -l > 934 > > Thank you
