Re: Isolating the Root Cause of "Connection Refused"

Eric, On 6/26/24 01:43, Eric Robinson wrote: What is impact on memory utilization if we increase the acceptCount value? There are 100 tomcat instances on the server. And would maxThreads have to be increased to accommodate the extra connections? After reading more, I guess that's a dumb questi

Re: Isolating the Root Cause of "Connection Refused"

Eric, On 6/25/24 20:10, Eric Robinson wrote: No - Tomcat passes the acceptCount value to the TCP/IP stack of the OS as part of listener socket initialization. I thought of that after I sent my previous message. the OS won't log this, since it's considered to be an application error. Assum

Re: Isolating the Root Cause of "Connection Refused"

Eric, On 6/25/24 14:22, Chuck Caldarale wrote: On Jun 25, 2024, at 13:12, Eric Robinson wrote: I'm obviously not getting something. If I understand correctly, the purpose of the acceptCount param is to allow tomcat to reject connections even after the TCP stack has passed them to the java

RE: Isolating the Root Cause of "Connection Refused"

> What is impact on memory utilization if we increase the acceptCount value? > There are 100 tomcat instances on the server. And would maxThreads have to > be increased to accommodate the extra connections? After reading more, I guess that's a dumb question. I'm trying to prevent connections from

RE: Isolating the Root Cause of "Connection Refused"

> > No - Tomcat passes the acceptCount value to the TCP/IP stack of the OS as > part of listener socket initialization. I thought of that after I sent my previous message. > the OS won't log this, since it's considered to be an application error. Assuming the problem is the acceptCount value, th

Re: Isolating the Root Cause of "Connection Refused"

> On Jun 25, 2024, at 13:12, Eric Robinson wrote: > > I'm obviously not getting something. If I understand correctly, the purpose > of the acceptCount param is to allow tomcat to reject connections even after > the TCP stack has passed them to the java process. At that point, the request > ha

RE: Isolating the Root Cause of "Connection Refused"

> -Original Message- > From: Chuck Caldarale > Sent: Tuesday, June 25, 2024 11:01 AM > To: Tomcat Users List > Subject: Re: Isolating the Root Cause of "Connection Refused" > > > > On Jun 25, 2024, at 12:55, Eric Robinson > wrote: > > > &

Re: Isolating the Root Cause of "Connection Refused"

> On Jun 25, 2024, at 12:55, Eric Robinson wrote: > >> You might still be running into the acceptCount limit on the . The >> default value is 100, so if more connection requests arrive in between the >> TCP/IP stack passing them on to the listening process, some could still be >> getting rejecte

RE: Isolating the Root Cause of "Connection Refused"

> -Original Message- > From: Chuck Caldarale > Sent: Monday, June 24, 2024 2:51 PM > To: Tomcat Users List > Subject: Re: Isolating the Root Cause of "Connection Refused" > > > > On Jun 24, 2024, at 16:40, Eric Robinson > wrote: > > >

Re: Isolating the Root Cause of "Connection Refused"

> On Jun 24, 2024, at 16:40, Eric Robinson wrote: > > I wrote a script that checks the FD counts for every java pid on the server. > Just looking at these results, I don't think we're hitting an FD limit at the > moment, but I'll try it again tomorrow while the problem is presenting. Quite

RE: Isolating the Root Cause of "Connection Refused"

ist > Subject: Re: Isolating the Root Cause of "Connection Refused" > > > > On Jun 24, 2024, at 15:47, Eric Robinson wrote: > > > >> -Original Message- > >> From: Chuck Caldarale > >> Sent: Monday, June 24, 2024 1:40 PM > >> T

Re: Isolating the Root Cause of "Connection Refused"

> On Jun 24, 2024, at 15:47, Eric Robinson wrote: > >> -Original Message- >> From: Chuck Caldarale >> Sent: Monday, June 24, 2024 1:40 PM >> To: Tomcat Users List >> Subject: Re: Isolating the Root Cause of "Connection Refused" >&g

RE: Isolating the Root Cause of "Connection Refused"

inson : >> -Original Message- >> From: Chuck Caldarale >> Sent: Monday, June 24, 2024 1:40 PM >> To: Tomcat Users List >> Subject: Re: Isolating the Root Cause of "Connection Refused" >> >> >> > On Jun 24, 2024, at 15:36, Eric Robins

RE: Isolating the Root Cause of "Connection Refused"

> -Original Message- > From: Chuck Caldarale > Sent: Monday, June 24, 2024 1:40 PM > To: Tomcat Users List > Subject: Re: Isolating the Root Cause of "Connection Refused" > > > > On Jun 24, 2024, at 15:36, Eric Robinson wrote: > > >

Re: Isolating the Root Cause of "Connection Refused"

> On Jun 24, 2024, at 15:36, Eric Robinson wrote: > >> -Original Message- >> From: Chuck Caldarale >> Sent: Monday, June 24, 2024 1:29 PM >> To: Tomcat Users List >> Subject: Re: Isolating the Root Cause of "Connection Refused" >&g

RE: Isolating the Root Cause of "Connection Refused"

> -Original Message- > From: Chuck Caldarale > Sent: Monday, June 24, 2024 1:29 PM > To: Tomcat Users List > Subject: Re: Isolating the Root Cause of "Connection Refused" > > > > On Jun 24, 2024, at 15:19, Eric Robinson wrote: > > > >

Re: Isolating the Root Cause of "Connection Refused"

> On Jun 24, 2024, at 15:19, Eric Robinson wrote: > > We have a tomcat server that is not that busy. It has 100 tomcat instances > running, but it handles a few hundred connections per second total, across > all of them. It intermittently rejects connection attempts to listening > tomcats. T

Isolating the Root Cause of "Connection Refused"

We have a tomcat server that is not that busy. It has 100 tomcat instances running, but it handles a few hundred connections per second total, across all of them. It intermittently rejects connection attempts to listening tomcats. The server is running Rocky 8, has 48 cores (about 15-40% utilize