-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Norbert,
On 8/16/20 13:16, Norbert Elbanbuena 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
rbert
-Original Message-
From: Paul Carter-Brown
Sent: Sunday, August 16, 2020 2:43 PM
To: Tomcat Users List
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 c
192.168.1.50:443199.189.191.86:51716CLOSE_WAIT
tcp6 202 0 192.168.1.50:443199.189.191.86:1386 CLOSE_WAIT
Warm regards,
Norbert
-Original Message-
From: Paul Carter-Brown
Sent: Sunday, August 16, 2020 2:43 PM
To: Tomcat Users List
Subject: Re: Tomcat
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
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
