PM02784: OUTOFMEMORYERROR RESULTS IN INCORRECT MESSAGES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Error Message: OutOfMemoryError does not result in a heap dump
    every time.Running with
    JAVA_DUMP_OPTS="ONOUTOFMEMORY(heapdump<OSB>3<CSB>)" and
    executing the a test case that creates OOM does not result in 3
    heap dumps as specified through the JAVA_DUMP_OPTS option.
    .
    Stack Trace: Running TestHeapExhaustion
    byte array allocated ok
    JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
    JVMDG315: JVM Requesting Heap dump file
    JVMDG318: Heap dump file written to
    /u/bordoli/src/dumps/HEAPDUMP.20061106.132552.33685587.phd
    JVMDG303: JVM Requesting Java core file
    JVMDG304: Java core file written to
    /u/bordoli/src/dumps/JAVADUMP.20061106.132552.33685587.txt
    JVMDG274: Dump Handler has Processed OutOfMemory.
    JVMST109: Insufficient space in Javaheap to satisfy allocation
    request
    Caught OOM #1
    byte array allocated ok
    JVMST109: Insufficient space in Javaheap to satisfy allocation
    request
    Caught OOM #2
    byte array allocated ok
    JVMST109: Insufficient space in Javaheap to satisfy allocation
    request
    Caught OOM #3
    byte array allocated ok
    JVMST109: Insufficient space in Javaheap to satisfy allocation
    request
    Caught OOM #4
    byte array allocated ok
    JVMST109: Insufficient space in Javaheap to satisfy allocation
    request
    Caught OOM #5
    done.
    .
    NA
    

Local fix

  • NA
    

Problem summary

  • The OutOfMemoryErrors thrown were due to
    1)no space available for making the allocation requested and
    2)whenever we were running dangerously short on memory
    In the second case, the messages that were given out were
    incorrect which did not clearly specify the reason for the OOM.
    

Problem conclusion

  • This defect will be fixed in:
    1.4.2 SR13 FP5
    .
    The fix deals with correcting the messages thrown when an
    OutOfMemoryError happens.The fix indicates the exact reason of
    the OOM. If the OOM is due to low memory available then -
    For example:
    <AF<OSB>12<CSB>: Allocation Failure. need 10016 bytes, 68 ms
    since last AF>
    <AF<OSB>12<CSB>: managing allocation failure, action=1
    (35024/63689704) (0/3352088)>
      <GC(13): GC cycle started Fri Nov 27 15:31:27 2009
      <GC(13): freed 0 bytes, 0% free (27616/67041792), in 382 ms>
      <GC(13): mark: 342 ms, sweep: 1 ms, compact: 39 ms>
      <GC(13): refs: soft 0 (age >= 6), weak 0, final 0, phantom 0>
      <GC(13): moved 8643 objects, 51929376 bytes, reason=1, used
    6944 more bytes>
    <AF<OSB>12<CSB>: managing allocation failure, action=3
    (27616/67041792)>
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM02784

  • Reported component name

    JAVA(1.3/1.4 CO

  • Reported component ID

    5648C9800

  • Reported release

    42A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-04

  • Closed date

    2010-02-23

  • Last modified date

    2010-06-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    JAVA(1.3/1.4 CO

  • Fixed component ID

    5648C9800

Applicable component levels

  • R42A PSN

       UP

  • R42L PSN

       UP

  • R42W PSN

       UP

  • R420 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

1.4.2

Reference #:

PM02784

Modified date:

2010-06-20

Translate my page

Machine Translation

Content navigation