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


  1.  Home
  2. JAVA400-L
  3. May 2009

Re: Java application cpu utilization spiking ... taking a long time tocancel.

Joe Sam Shirah wrote:
Probably garbage collection,

That's pretty much the path I've been going down ... unfortunately the diagnostics that the classic JVM provides for garbage collection are pretty light weight.

I have asked if they can install the 32bit JVM ... but getting system configuration changes is kind of hard.

I went through a similar issue with WAS over the last few months.
The asynch collector can really run into problems if it can't
complete (usually do to disk swap) before another memory allocation
request comes through. It's very similar to thrashing.

I'm going to ask the customer if they can increase the amount of memory allocated to the subsystem the application is running in.

The ENDJOB doesn't appear to take effect because it wants to clean up
the memory before responding.

Even if it's an immediate end? IIRC, the customer also reported that the application took a long time to die if an ENDJOBABN was used.

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.