IBM Support

IZ42683: JVM OUTOFMEMORY DURING COMMAND 'TACMD EXPORTWORKSPACES'

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem Description:
    JVM heap size can not be changed because the setting is
    hardcoded inside the tacmd exportworkspaces code.
    
    This behaviour has been changed starting from ITM 6.2.1
    (TACMD_JVM_MAX_MEMORY env. setting) with defect 69862 that has
    to be back ported for the customer.
    
    Detailed Recreation Procedure:
    Create a large number of workspaces to be exported, the Java
    heap size upper limit is 256M
    
    Related Files and Output:
    Output from tacmd
    
    tacmd exportworkspaces -x works.xml -s 10.240.19.90 -u rx0555
    
    VMDG315: JVM Requesting Heap dump file
    ..........................JVMDG318: Heap dump file written to C:
    \wk\heapdump.20081029.102420.4216.phd
    VMDG303: JVM Requesting Java core file
    VMDG304: Java core file written to
    C:\wk\javacore.20081029.102425.4216.txt
    VMDG274: Dump Handler has Processed OutOfMemory.
    VMST109: Insufficient space in Javaheap to satisfy allocation
    request
    VMST109: Insufficient space in Javaheap to satisfy allocation
    request
    VMST109: Insufficient space in Javaheap to satisfy allocation
    request
    

Local fix

  • NA
    

Problem summary

  • tacmd exportworkspaces command does not work when there are a
    large or complex number of workspaces to be exported.
    
    The problem  is caused by insufficient JVM heap size setting.
    JVM heap size can not be changed because the setting is
    hardcoded inside the tacmd exportworkspaces code. This behaviour
    has been changed starting from ITM 6.2.1
    (TACMD_JVM_MAX_MEMORY env. variable setting) with defect 69862
    that has been back ported to ITM 6.1 FP7 for the customer.
    

Problem conclusion

  • The code change is to check and use an env. global variable
    setting TACMD_JVM_MAX_MEMORY to let user possibly increase the
    setting for JVM max heap size.
    If TACMD_JVM_MAX_MEMORY  is defined, it retrieves the value,
    check that it is an allowed value and use this to invoke the
    java command with the parameter -Xmx
    
    The fix for this APAR will be included in the following
    maintenance vehicle:
        | interim fix | 6.1.0.7-TIV-ITM-IF0004
    
    Note: Search the IBM Technical support web site for maintenance
    package availability
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ42683

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-28

  • Closed date

    2009-03-04

  • Last modified date

    2009-03-04

  • 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

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

  • R610 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCTLMP","label":"ITM Tivoli Enterprise Mgmt Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 March 2009