Re: Checking a JVM for out-of-memory? -- JAVA400-L

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

Subject: Re: Checking a JVM for out-of-memory?
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Mon, 24 Mar 2014 13:39:09 -0500
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the IBM i <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

On 3/24/2014 1:27 PM, James H. H. Lampert wrote:

Is there anything OS/400-specific for detecting an out-of-memory
condition on a JVM job?

I'm not 100% sure, but I don't think you can actually run out of memory with the IBM i JVM.

I think you can use so much memory that the job starts paging memory in & out at a rate that causes performance problems.

I could be wrong.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Checking a JVM for out-of-memory? , Dan Kimmel

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.