IBM Support

PM54665: PROVIDE ADDITIONAL DIAGNOSTIC OPTIONS FOR DEALING WITH A JVM OUT OFMEMORY CONDITION ON WEBSPHERE APPLICATION SERVER FOR Z/OS.

Fixes are available

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The way in which JVM OutOfMemory conditions surface is
    dependent on what area of code first deals with the condition,
    which prevents WebSphere for z/OS customers from writing
    effective automation tasks to deal with the situation.
    Additional diagnostic options need to be provided.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 and V8.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The external symptom of JVM             *
    *                      OutOfMemory errors can vary, making     *
    *                      it difficult to write automation        *
    *                      tasks to recover from them.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Depending on the area of code that encounters a JVM
    OutOfMemory condition, the external symptom can vary.  In some
    cases, no error message is produced at all, and in other cases
    messages may be written to the system log.  A consistent way
    of catching and reporting OutOfMemory conditions is required
    in order to write automation tasks to deal with them.
    

Problem conclusion

  • Numerous configurable diagnostic options were added to report
    JVM OutOfMemory conditions and to automatically issue SVCDUMPs
    when they occur.
    
    APAR PM54665 requires changes to documentation.
    
    NOTE: Periodically, we refresh the documentation on our Web
    site, so the changes might have been made before you
    read this text. To access the latest on-line
    documentation, go to the product library page at:
    
    http://www.ibm.com/software/webservers/appserv/library
    
    The following changes to the WebSphere Application Server
    Version 7.0 Information Center will be made available in May,
    2012.
    
    The topic "Error minor codes" will be updated to include the
    following description of the C9C2704B error minor code:
    
    C9C2704B
    Explanation: The Java Virtual Machine in this server is out
    of memory.  An SVCDUMP was issued as a result of  the
    ras_java_oom_action environment variable.
    Suggested Action: The SVCDUMP can be used to analyze memory
    usage in the affected JVM.  There may be a memory leak, or the
    JVM may need a larger heap size.
    
    The topic "Modify command" will be updated to include the
    following description of the new JAVAOOM parameter:
    
    JAVAOOM,[INTERVAL=nnn | ACTION=xxx | RESET]
    
    Used to dynamically alter the diagnostic action that is taken
    if a Java Virtual Machine (JVM) out-of-memory condition occurs
    in this server. It is also used to dynamically alter     the
    time interval within which the diagnostic action is repeated.
    
    Specifying INTERVAL sets the amount of time, in seconds,
    during which a diagnostic action is not repeated. This
    attribute overrides the value specified for the
    ras_java_oom_interval environment variable.
    
    Specifying ACTION sets the diagnostic action that is taken
    when a JVM out-of-memory condition occurs in this server. This
    attribute overrides the value specified for the
    ras_java_oom_action environment variable. One of the following
    values can be specified as the value for xxx:
    
        NONE
            No diagnostic action is performed.
        WTO
            A BBOO0404E error message is written to hardcopy.
        SVCDUMP
            An SVCDUMP of the affected address space is taken,
    with minor code C9C2704B.
    
    Specifying RESET Resets the diagnostic action and interval to
    the values specified for the ras_java_oom_action and
    ras_java_oom_interval environment variables.
    
    The topic "Display command" with examples" will be updated to
    include the following description of the new section:
    
    "Display the diagnostic action for a JVM out-of-memory
    condition"
    
    To display the diagnostic action that will be taken if a Java
    Virtual Machine (JVM) out-of-memory condition occurs in this
    server, along with the interval within which the diagnostic
    action is not repeated, use the following command:
    
    f server,display,javaoom
    One of the following values displays:
    NONE - No diagnostic action is performed.
    WTO - A BBOO0404E error message is written to hardcopy.
    SVCDUMP - An SVCDUMP of the affected address space is taken,
    with minor code C9C2704B.
    
    The topic "Application server custom properties for z/OS" will
    be updated to include the following descriptions of two new
    custom properties:
    
    ras_java_oom_action
    Specifies the type of diagnostic action that is performed when
    a Java Virtual Machine out-of-memory condition occurs.
    The possible values are:
    NONE - No diagnostic action is performed.
    WTO - A BBOO0404E error message is written to hardcopy.
    SVCDUMP - An SVCDUMP of the affected address space is taken,
    with minor code C9C2704B.
    
    Data type - String
    Default - NONE
    Used by Daemon - Yes
    
    ras_java_oom_interval
    Specifies, in seconds, the length of time during which the
    diagnostic action specified by the ras_java_oom_action
    environment variable is not repeated. This property helps to
    limit the number of diagnostic actions that occur for related
    out-of-memory conditions.
    Data type - Integer
    Range - 0 - 65535
    Default - 600
    Used by Daemon - Yes
    
    APAR PM54665 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.23 of WebSphere Application Server V7.0
    and Fix Pack 8.0.0.3 of WebSphere Application Server V8.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM54665

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-19

  • Closed date

    2012-04-25

  • Last modified date

    2012-10-10

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK78616

       UP12/05/26 P F205

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021