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 > >
