Hi Mark, thanks a lot. here come the dumps:
Josep *Josep M Beleta* *Director de Tecnologia* Carver Advanced Systems, S.L. París, 184. 4º 08036 - Barcelona Tel: 93 238 5880 Fax: 93 238 5881 *segueix-nos <http://www.linkedin.com/company/carver-advanced-systems-s.l.>* <http://twitter.com/#%21/carver_as> <https://plus.google.com/112583630853594851700?prsrc=3> www.carver-as.com 2016-04-12 20:43 GMT+02:00 Mark Thomas <ma...@apache.org>: > On 12/04/2016 19:30, Josep M Beleta wrote: > > Hi, > > > > I need some help with a problem we have running Tomcat 8, with Java 8 on > > a Windows 2008 R2 Standard with Service Pack 1 running as a virtual > > machine on top of ESXi, 5.1.0. The virtual machine has 16 GB of memory > > and 4 CPUs. The physical host computer has lots of memory and is not > > stressed at all. > > > > One week ago our Tomcats, we have two, began to use high CPU. When the > > problem started we had no made any change we can remember in the > > preceding week, and no Windows update was installed. > > > > We use two Tomcats, one of them with some in-house applications the > > other one with Jira. Both began to shows the same symptoms roughly at > > the same time. > > > > The Jira Tomcat version is 8.0.17 and runs with Java 1.8.0_51 64 Bit, > > the other Tomcat is 8.0.33 and runs over Java 1.8.0_77 64 Bit. > > > > These are the facts we can summarize: > > > > 1. Now we run only the Tomcat for our in-house applications.We stopped > > the Jira one. > > 2. We run it as a service. > > 3. Every time, two hours after launching the Tomcat service, the CPU > > use jumps to 70-75% and some time after (one hour more) it reaches > > 100 %. More threads are allocated using lots of CPU. The final > > result is our entire system being degraded as time goes on. > > 4. The problems has nothing to do with our applications. We undeployed > > them with the same result. > > 5. We tested versions 8.0.23 and 8.0.33 in our internal Tomcat with the > > same results. > > 6. We tested JVM 1.8.0_66, 1.8.0_71 and 1.8.0_77 with the same results. > > 7. We have changed some JVM parameters, allocating more heap memory, or > > changing GC methods with always the same result, 100% CPU. > > 8. Using jstack we take several thread dumps that we are enclosing in > > this message. Dump75 is whe the CPU was at 75 %, the other one, > > Dump100, the CPU was at 100%. > > 9. I am attaching the Process Explorer images of the Tomcat process > > showing also the Tomcat threads. I am including a Tomcat manager > > screenshot showing the status of the server. > > > > Any help would be deeply appreciated, > > We really need to see those thread dumps. I've checked the list config > and plain text files should be allowed through. I'm attaching a test > file to this message to confirm that. If it comes through, please > provide your thread dumps in plain text form and we can take a look. > > Mark > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
