t; Sent: Monday, November 22, 2021 10:19 AM
> To: dev@geode.apache.org
> Subject: Re: Open socket handles build up over time (leaking?)
>
> Hi,
>
> Bug ticket:
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-98
filing the ticket and for looking into the additional leak
>
> From: Leon Finker
> Sent: Monday, November 22, 2021 10:19 AM
> To: dev@geode.apache.org
> Subject: Re: Open socket handles build up over time (leaking?)
>
> Hi,
>
Thanks for filing the ticket and for looking into the additional leak
From: Leon Finker
Sent: Monday, November 22, 2021 10:19 AM
To: dev@geode.apache.org
Subject: Re: Open socket handles build up over time (leaking?)
Hi,
Bug ticket:
https://nam04
de bug ticket
>
> From: Leon Finker
> Sent: Wednesday, November 17, 2021 1:13 PM
> To: dev@geode.apache.org
> Subject: Re: Open socket handles build up over time (leaking?)
>
> Thank you! I'll try to test this change. What's the procedure for
Yes, open a geode bug ticket
From: Leon Finker
Sent: Wednesday, November 17, 2021 1:13 PM
To: dev@geode.apache.org
Subject: Re: Open socket handles build up over time (leaking?)
Thank you! I'll try to test this change. What's the procedure for
this? Should I
> From: Leon Finker
> Sent: Wednesday, November 17, 2021 10:30 AM
> To: dev@geode.apache.org
> Subject: Re: Open socket handles build up over time (leaking?)
>
> Following Darrel's excellent advice :) I think I tracked down the area
> of the socket handle
ostAuthorization it should do the followiing:
> > if (unsuccessfulMsg != null) {
> > try {
> >socket.close();
> > } catch (IOException ignore) {
> > }
> > } else {
> >performPostAuthorization(...)
> > }
> > _
ization(...)
> }
>
> From: Leon Finker
> Sent: Wednesday, November 17, 2021 10:30 AM
> To: dev@geode.apache.org
> Subject: Re: Open socket handles build up over time (leaking?)
>
> Following Darrel's excellent advice :) I think I tracke
{
performPostAuthorization(...)
}
From: Leon Finker
Sent: Wednesday, November 17, 2021 10:30 AM
To: dev@geode.apache.org
Subject: Re: Open socket handles build up over time (leaking?)
Following Darrel's excellent advice :) I think I tracked down the area
of the socket handle lea
ervices on the
> > website. Some examples include: cookies used to analyze site traffic,
> > cookies used for market research, and cookies used to display advertising
> > that is not directed to a particular individual.
> > help.mulesoft.com
> >
> > _______
raffic, cookies
> used for market research, and cookies used to display advertising that is not
> directed to a particular individual.
> help.mulesoft.com
>
>
> From: Leon Finker
> Sent: Tuesday, November 16, 2021 9:28 AM
> To: dev@geode.ap
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
_
From: Leon Finker
Sent: Tuesday, November 16, 2021 9:28 AM
To: dev@geode.apache.org
Subject: 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 s
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
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
15 matches
Mail list logo
