Stephen,
On 6/29/24 07:57, Stephen Stevie wrote:
Tomcat not configured on default port
Which port is most often showing in the CLOSE_WAIT state?
[...] it was working fine until the start of this year. After that,
it was once a month and now every alternate day, we are seeing this.
Has
Tomcat not configured on default port
On Thu, Jun 27, 2024 at 9:58 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Stephen,
>
> On 6/26/24 01:18, Stephen Stevie wrote:
> > We are using Apache Tomcat 8.5.49 and sometimes in a day, we see the
> > application is going unresponsiv
This was working fine for the last 2-3 years and no change in the server
configs at all. This started all of a sudden.
On Wed, Jun 26, 2024 at 7:02 PM Chuck Caldarale wrote:
>
> > On Jun 26, 2024, at 00:18, Stephen Stevie
> wrote:
> >
> > We are using Apache Tomcat 8.5.49
>
>
> Stop right there
Stephen,
On 6/26/24 01:18, Stephen Stevie wrote:
We are using Apache Tomcat 8.5.49 and sometimes in a day, we see the
application is going unresponsive though the service is up and running and
giving 503 (service unavailable error). When netstat for the port is run,
we see many CLOSE_WAIT connec
Stephen,
On 6/26/24 09:31, Chuck Caldarale wrote:
On Jun 26, 2024, at 00:18, Stephen Stevie
wrote:
We are using Apache Tomcat 8.5.49
Stop right there. Tomcat 8.5.x reached end-of-life earlier this year
and is no longer supported. The particular version you’re running is
over 4.5 years old
> On Jun 26, 2024, at 00:18, Stephen Stevie wrote:
>
> We are using Apache Tomcat 8.5.49
Stop right there. Tomcat 8.5.x reached end-of-life earlier this year and is no
longer supported. The particular version you’re running is over 4.5 years old,
and many, many security and correctness fixe
