IBM JDK Crashes And Generates Java Core When Allocating Large Objects In Heap (Doc ID 1115503.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version 10.1.2.2.0 to 10.1.2.3.0 [Release AS10gR2]
Information in this document applies to any platform.
***Checked for relevance on 04-Feb-2013***

Symptoms


Running Applications deployed in OC4J/OAS 10.1.2 with IBM JDK 1.4.2. When the JVM tries to allocate space in the Heap for a large object, it crashes and generates java-core and heap-dump files although the Heap has enough space for the large object. Increasing the Heap Size doesn't help. The javacore file shows:


1TISIGINFO OUTOFMEMORY received
[..]
1XHSIGRECV Unexpected signal -1 received at 0x0 in <unknown>. Processing terminated.


The GC logs - enabled by (-verbose:gc) - shows:

<AF[5]: Allocation Failure. need 2083048 bytes, 8127174 ms since last AF>
<AF[5]: managing allocation failure, action=2 (253433944/536803840)>
<AF[5]: completed in 80 ms>

<AF[6]: Allocation Failure. need 5498928 bytes, 2665974 ms since last AF>
<AF[6]: managing allocation failure, action=2 (382089984/536803840)>
<AF[6]: completed in 77 ms>

<AF[7]: Allocation Failure. need 8192 bytes, 375728 ms since last AF>
<AF[7]: managing allocation failure, action=0 (460890248/536803840)>
<AF[7]: completed in 64 ms>

<AF[8]: Allocation Failure. need 6455416 bytes, 11534074 ms since last AF>
<AF[8]: managing allocation failure, action=2 (194364344/536803840)>
<AF[8]: completed in 98 ms>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms