Hi,
We are encountering the following deadlock (pretty often) on 1.13.1:
1. Client (bridge) acceptor thread is locked up in this stack
"Handshaker 0.0.0.0/0.0.0.0:40011 Thread 2" #219 daemon prio=5
os_prio=0 tid=0x7f755c007000 nid=0x44a2 runnable
[0x7f75847c7000]
java.lang.Thread.Stat
Hi,
In AcceptorImpl.run, the accepted client socket seems to only be
closed when there is IOException. I can't prove it, but I think there
can sometimes be non IO exception here as well and then the client
socket will not be closed? Also, can we please add a catch for other
kinds of exceptions and
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 Ac
ut 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 N
alyze site traffic, 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
> T
mes due to
race conditions with reconnects (I think). It's not happening all the
time. It's not causing any problems to the client in general. But the
server leak eventually causes us to run out of file handles for the
process :(
Thank you!
On Tue, Nov 16, 2021 at 4:33 PM Leon Finker
formPostAuthorization it should do the followiing:
> > if (unsuccessfulMsg != null) {
> > try {
> >socket.close();
> > } catch (IOException ignore) {
> > }
> > } else {
> >performPostAuthorization(...)
> > }
> >
". I think right before it calls performPostAuthorization it
> should do the followiing:
> if (unsuccessfulMsg != null) {
> try {
> socket.close();
> } catch (IOException ignore) {
> }
> } else {
> performPostAuthorization(...)
> }
> _
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
>
> 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 (leak
nt of that log warning to the metric
of leaked socket handles, it seems to correlate.
Thank you in advance
On Mon, Nov 22, 2021 at 1:45 PM Darrel Schneider wrote:
>
> Thanks for filing the ticket and for looking into the additional leak
> ____
> From: Leon
11 matches
Mail list logo
