×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Last night, we switched the customer box in question from running Tomcat
under Java 7 (64-bit) to Java 8 (64-bit), and all day today, the
processor load from the Tomcat server has been dramatically lighter. I
haven't seen the overall CPU over around 70% today, and haven't seen the
Tomcat's JVM job usage over 30% (as I type this, the overall is at
48.1%, of which the JVM job is a mere 7.8%), where before, it was
peaking at full saturation, with the Tomcat JVM job alone accounting for
as much as 90% or more.
I am cautious about this, but I think maybe just the switch to Java 8
alone has solved the problem.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This thread ...
JVM job for Tomcat taking lots and lots of CPU, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
