Hi Paul, Yes these are some samples, I have about 300 of them getting stuck hourly
tcp 761 0 192.168.1.50:58870 74.112.28.109:8011 CLOSE_WAIT tcp 0 0 192.168.1.50:56938 192.168.1.50:61616 CLOSE_WAIT tcp 0 0 192.168.1.50:56924 192.168.1.50:61616 CLOSE_WAIT tcp 0 0 192.168.1.50:56910 192.168.1.50:61616 CLOSE_WAIT tcp 0 0 192.168.1.50:56912 192.168.1.50:61616 CLOSE_WAIT tcp6 0 6240 192.168.1.50:443 52.11.72.45:47123 CLOSE_WAIT tcp6 32 0 192.168.1.50:443 34.209.104.242:13402 CLOSE_WAIT tcp6 268 0 192.168.1.50:443 108.162.244.28:40864 CLOSE_WAIT tcp6 32 0 192.168.1.50:443 35.167.185.49:10019 CLOSE_WAIT tcp6 32 0 192.168.1.50:443 52.24.48.141:60660 CLOSE_WAIT tcp6 202 0 192.168.1.50:443 199.189.191.86:51716 CLOSE_WAIT tcp6 202 0 192.168.1.50:443 199.189.191.86:1386 CLOSE_WAIT Warm regards, Norbert -----Original Message----- From: Paul Carter-Brown <paul.carter-br...@jini.guru> Sent: Sunday, August 16, 2020 2:43 PM To: Tomcat Users List <users@tomcat.apache.org> Subject: Re: Tomcat Handling close_waits Hi Norbert, The TCP socket states and timers are managed by the underlying OS and not by Tomcat. Can you paste a netstat -an result so I can see what you mean. Also, is the client using HTTP 1.1 with keep-alive or not? What kind of traffic is this? Paul On Sun, Aug 16, 2020 at 7:16 PM Norbert Elbanbuena <norb...@teligentip.com> wrote: > I also noticed that while server receives the connection requests, we > are seeing multiple requests from the same sources. Some same source > requests > (FIN-WAIT) are all in state while other same sources requests are in > other state (some in FIN-WAIT or close_wait and some Established). > > Why are we seeing multiple requests from the same source at the same time? > Doesn't each socket request exhaust a thread on the application? > > > Warm regards, > > Norbert Elbanbuena > > -----Original Message----- > From: Norbert Elbanbuena <norb...@teligentip.com> > Sent: Sunday, August 16, 2020 11:35 AM > To: Tomcat Users List <users@tomcat.apache.org> > Subject: Tomcat Handling close_waits > > Hi, > > We are experiencing a flood of close_waits in our server. > Interestingly, all of the sessions stuck in close_waits are sourced > from Amazon IP addresses. Our second server running the same setup > (hardware spec, OS version, Tomcat version, etc.) and had almost the > same session count and our application and Tomcat didn't go unresponsive. > > Is there any tuneable parameter for the APR connector for Tomcat to > close the stuck sessions, rather than waiting for the application? > > Warm regards, > > Norbert Elbanbuena > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
