Re: Unexpected JVM crash, assistance requested -- 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: Unexpected JVM crash, assistance requested
From: Steve Hinrichs <Steve.Hinrichs@xxxxxxxxxxxxxxx>
Date: Thu, 15 Nov 2018 22:26:12 +0000
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

Hi Matt,

Nothing stands out as an obvious item. Have you run the dumps through a HeapAnalyzer? I have used an IBM HeapAnalyzer in the past to look for a memory leaks.
It appears to possible be related to garbage collection and JIT compiling?? I have seen core and snap dumps before, but I have never seen a jitdump!

I am curious why the max memory is set to 2G? -Xmx2G
Maybe try 1G?

Steve

As an Amazon Associate we earn from qualifying purchases.

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.