× 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.



Ladies and Gentlemen:

We have a customer installation in which the JVM job for our Tomcat server is frequently using massive amounts of CPU.

It's Tomcat 7.0.67, running on an AS/400, in a 64-bit Java 7 JVM, with -Xms3096m and -Xmx5120m JVM arguments.

GC information on the JVM job shows:
Garbage collected heap: Initial heap size . . . . . . . . . : 3096.000M
Maximum heap size . . . . . . . . . : 5120.000M
Current heap size . . . . . . . . . : 4458.562M
Heap in use . . . . . . . . . . . . : 1907.673M
Other memory: Internal (break) memory size . . . . : 504.982M
JIT memory size . . . . . . . . . . : 74.000M
Shared classes memory size . . . . . : 0.000M
General GC information: Current GC cycle . . . . . . . . . . : 2184
GC policy type . . . . . . . . . . . : GENCON
Current GC cycle time . . . . . . . : 552
Accumulated GC time . . . . . . . . : 5108241

It seems to be doing a lot of garbage-collecting.

Would switching to Java 8 help? Would switching to 7.0.93 help?

--
James H. H. Lampert

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.