Async servlet non-blocking IO and request recycling

Hi, I have a question regarding async servlets and request recycling. In particular, I'm interested in request recycling by tomcat when an IO error occurs. In my use case, I'm using non-blocking reads with a ReadListener but blocking writes (no WriteListener). The main question can be summarized

Re: Class loader takes long time after server inactivity - Tomcat Version 9.0.10

On 14/01/2020 13:42, Niall Fitzpatrick wrote: > Hi Folks, > > > > I have a web application that, after a period of inactivity (1-2hours), will > stall for 3 – 35 seconds upon the first new session. All subsequent sessions > will not experience this delay unless another period of inactivity

Re: Class loader takes long time after server inactivity - Tomcat Version 9.0.10

> Hi Folks, > > > > I have a web application that, after a period of inactivity (1-2hours), will > stall for 3 – 35 seconds upon the first new session. All subsequent sessions > will not experience this delay unless another period of inactivity occurs. > > > > I’ve found that the delay

RE: Class loader takes long time after server inactivity - Tomcat Version 9.0.10

Hi, We have experienced similar behavior. I have posted previously about this issue so forgive me if I repeat myself here. Some background first based on our recent experiences. We noticed an increase in CPU usage and disk I/O after we migrated from Tomcat 7.0.55 to Tomcat 9.0.19. What

Class loader takes long time after server inactivity - Tomcat Version 9.0.10

Hi Folks, I have a web application that, after a period of inactivity (1-2hours), will stall for 3 – 35 seconds upon the first new session. All subsequent sessions will not experience this delay unless another period of inactivity occurs. I’ve found that the delay occurs when loading jars

Re: Class loader takes long time after server inactivity - Tomcat Version 9.0.10

Hey Niall, On Tue, 14 Jan 2020 at 13:42, Niall Fitzpatrick wrote: > Hi Folks, > > > > I have a web application that, after a period of inactivity (1-2hours), > will stall for 3 – 35 seconds upon the first new session. All subsequent > sessions will not experience this delay unless another

Re: Class loader takes long time after server inactivity - Tomcat Version 9.0.10

On 14/01/2020 14:40, Niall Fitzpatrick wrote: > > > > >> Hi Folks, >> >> >> >> I have a web application that, after a period of inactivity (1-2hours), will >> stall for 3 – 35 seconds upon the first new session. All subsequent sessions >> will not experience this delay unless another period

Re: Class loader takes long time after server inactivity - Tomcat Version 9.0.10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 1/14/20 9:58 AM, Mark Thomas wrote: > On 14/01/2020 14:40, Niall Fitzpatrick wrote: >> >> >> >> >>> Hi Folks, >>> >>> >>> >>> I have a web application that, after a period of inactivity >>> (1-2hours), will stall for 3 – 35 seconds

RE: Class loader takes long time after server inactivity - Tomcat Version 9.0.10

If it helps for reference Here is our singleton... import javax.xml.parsers.DocumentBuilderFactory; import javax.xml.transform.TransformerFactory; import javax.xml.xpath.XPathFactory; import javax.xml.xpath.XPathFactoryConfigurationException; /** * This class provides a set of methods to

Re: Class loader takes long time after server inactivity - Tomcat Version 9.0.10

From: Christopher Schultz Sent: 14 January 2020 16:30 To: users@tomcat.apache.org Subject: Re: Class loader takes long time after server inactivity - Tomcat Version 9.0.10 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 1/14/20 9:58 AM, Mark Thomas

Re: Encoding properties

On 14/01/2020 19:50, Luis Arriaga wrote: > Hi Apache team, Please don't cross-post. This discussion can continue on the dev list since you posted there first and it is related to changing the source code. > We are updating our encoding implementation on Tomcat and the ServiceNow > platform from

Encoding properties

Hi Apache team, We are updating our encoding implementation on Tomcat and the ServiceNow platform from ISO-8859-1 to UTF-8 and ran into some concerns. Our Tomcat setup includes 8.5.47 on a CentOS VM, where Tomcat serves as our Java Servlet Web Server and we terminate SSL on our load balancer.