Re: Added to Jira

Done! You should have access now. -Dan From: Kristen Oduca Sent: Tuesday, November 16, 2021 4:03 PM To: dev@geode.apache.org Subject: Added to Jira Hi, Can I be added to the Geode Jira so I can assign myself tasks? My username is kris10. Thanks, Kristen

Added to Jira

Hi, Can I be added to the Geode Jira so I can assign myself tasks? My username is kris10. Thanks, Kristen Oduca

Re: Open socket handles build up over time (leaking?)

Hi Darrel, Thank you! I'll try to track it! On Tue, Nov 16, 2021 at 2:42 PM Darrel Schneider wrote: > > This link: > https://help.mulesoft.com/s/article/How-to-identify-leaked-file-descriptors-that-are-shown-only-as-cant-identify-protocol-in-lsof > points out that once the fd gets into this

Re: Open socket handles build up over time (leaking?)

Hi Anthony, >- What OS for client and server? Server: CentOS release 6.10 Client: Windows 10 and CentOS 6.* The cache is connected to by durable and non durable clients. Durable clients connect from Windows 10. And non durable clients connect from backend CentOS servers. The server cache has no

Re: Open socket handles build up over time (leaking?)

This link: https://help.mulesoft.com/s/article/How-to-identify-leaked-file-descriptors-that-are-shown-only-as-cant-identify-protocol-in-lsof points out that once the fd gets into this "can't identify protocol" state you can no longer figure out things like what port(s) and addresses are

Re: Failed durable client connection initialization can sometimes leak client socket handle?

The run method on AcceptorImpl is run in a LoggingThread instance (see AcceptorImpl.start()). So any exceptions thrown by AcceptorImpl.run() will be logged as a fatal log message containing ""Uncaught exception in thread" by the LoggingThread. You can see the code that does this in

Re: Failed durable client connection initialization can sometimes leak client socket handle?

I just responded to your latest question, but if you have logs or a test case you could share that would be really helpful. Thanks, Anthony > On Nov 10, 2021, at 10:01 AM, Leon Finker wrote: > > Hi, > > In AcceptorImpl.run, the accepted client socket seems to only be > closed when there is

Re: Open socket handles build up over time (leaking?)

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

Open socket handles build up over time (leaking?)

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