IBM Support

PM12242: Out of memory error received running the VisualAge Generator to EGL migration tool

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Rational Business Developer V7.5.1.4:
    
    Out of memory error is received running the VisualAge Generator
    to EGL Stage 2/3 migration tool.
    
    The .log shows:
    
    !MESSAGE An internal error occurred during: "EGL Working Copy
    Resource Change Job ".
    !STACK 0
    java.lang.OutOfMemoryError
     at java.io.FileInputStream.readBytes(Native Method)
     at java.io.FileInputStream.read(Unknown Source)
     at java.io.BufferedInputStream.read1(Unknown Source)
     at java.io.BufferedInputStream.read(Unknown Source)
     at java.io.FilterInputStream.read(Unknown Source)
     at
    com.ibm.etools.edt.internal.core.ide.utils.Util.getFileContents(
    Unknown Source)
     at
    com.ibm.etools.edt.internal.core.ide.lookup.workingcopy.WorkingC
    opyResourceChangeProcessor$WorkingCopyResourceChangeJob.processA
    ddedFile(Unknown Source)
     at
    com.ibm.etools.edt.internal.core.ide.lookup.workingcopy.WorkingC
    opyResourceChangeProcessor$WorkingCopyResourceChangeJob.doRun(Un
    known Source)
     at
    com.ibm.etools.edt.internal.core.ide.lookup.workingcopy.WorkingC
    opyResourceChangeProcessor$WorkingCopyJob.runInWorkspace(Unknown
    Source)
     at
    org.eclipse.core.internal.resources.InternalWorkspaceJob.run(Unk
    nown Source)
     at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
    

Local fix

  • A temp fix is available from support.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    - Users affected: All of customers using the VAGen to EGL
    wizard to migrate code.
    - Problem description: This APAR is to solve the out of
    memory during the stage 2 of VAGen to EGL migration. The OOM
    exception maybe will not be thrown during the stage 2, more
    possiblely the OOM will be thrown after VAGen to EGL
    migration while compiling the workspace. This is because the
    leaked memory in the stage 2 is not released.
    

Problem conclusion

  • Code updated to release the leaked memory when internal
    strings.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM12242

  • Reported component name

    VAGEN2RBD MIGRA

  • Reported component ID

    5724S5002

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-14

  • Closed date

    2010-10-14

  • Last modified date

    2010-10-14

  • 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

    VAGEN2RBD MIGRA

  • Fixed component ID

    5724S5002

Applicable component levels

  • R751 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
14 October 2010