Thanks for your input on this issue. I have additional information on this. What would happen if the temp directory gets this size of 38000 Files and 1.6GB of data? Has anyone seen tomcat slow down because of temp directory size?
On Sun, Mar 9, 2025 at 1:01 PM Suvendu Sekhar Mondal <suv3...@gmail.com> wrote: > Hi Timothy, > > Since you are running Tomcat on Windows Server 2016, I'll suggest to > capture OS level CPU utilization by threads and then tally them with the > threads in Java thread dumps to identify the cause. > > Run Process Explorer as an administrator. Right-click the process, select > Properties, and then select the Threads tab. Sort by CPU column and note > thread ID. Note top CPU consuming thread IDs. Convert those numbers to hex > values and search it in the thread dumps. > > On Sat, Mar 8, 2025, 5:31 AM Christopher Schultz < > ch...@christopherschultz.net> wrote: > > > Chuck, > > > > On 3/7/25 5:38 PM, Chuck Caldarale wrote: > > > > > >> On 2025 Mar 7, at 16:06, Timothy Resh <mresh1...@gmail.com> wrote: > > >> > > >> Dear Apache Support Team, > > >> > > >> I'm running Tomcat 9.0.98 in the AWS Cloud. After several days of use, > > we > > >> see that the CPU utilization eventually reaches 100% in the Cloud, but > > when > > >> we RDP into the Server and look at the Task Manager, we do not see the > > >> performance being impacted. However, users complain of severe > slowdowns, > > >> and sometimes, it stops responding. > > >> > > >> We are trying to discover what may be the issue. We have an automated > > >> process that will fire off a restart when it reaches 100% utilization. > > We > > >> want to get more information by using a JPS, Jconsole, or some other > > Java > > >> utility to capture additional information before the restart. Do you > > have > > >> any suggestions in capturing this information before restart? > > > > > > Try taking several full thread dumps a few seconds apart to see > > > where threads are executing. You can use a profiler if you have one, > > > the jcmd or jstack JDK utilities, or VisualVM (separate download, > > > these days). The jconsole utility can also be used to look at each > > > individual thread one by one, but that’s somewhat painful. VisualVM > > > can let you determine quickly by eye which threads are burning up > > > the CPU. > > > > +1 > > > > With 11 web applications deployed, you may have some performance issues > > if you have a lot of scannable files and you are using reloadable="true" > > in META-INF/context.xml. > > > > But a thread dump is going to be very informative. > > > > -chris > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > >
