IBM Support

Out of memory error when installing an HF on MCF v8.0

Troubleshooting


Problem

Out of memory error when installing an HF on MCF v8.0

Symptom

The HF installation goes out of memory while executing the “munge” target from xapiDeployer.xml.
It throws the stack trace shown below.
Error Message
[exec] munge:
[exec] <INSTALL_DIR>/properties/xapiDeployer.xml:174: java.lang.OutOfMemoryError
[exec] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:115)
[exec] at org.apache.tools.ant.Task.perform(Task.java:348)
[exec] at org.apache.tools.ant.Target.execute(Target.java:357)
[exec] at org.apache.tools.ant.Target.performTasks(Target.java:385)
[exec] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
[exec] at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
[exec] at com.sterlingcommerce.woodstock.install.deployer.AntDeployer.executeScript(AntDep loyer.java:240)
[exec] at com.sterlingcommerce.woodstock.install.deployer.AntDeployer.deploy(AntDeployer.j ava:197)
[exec] at com.sterlingcommerce.woodstock.install.deployer.AntDeployer.execute(AntDeployer. java:193)
[exec] at com.sterlingcommerce.woodstock.install.deployer.AntDeployer.main(AntDeployer.jav a:180)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav a:43)
[exec] at java.lang.reflect.Method.invoke(Method.java:615)
[exec] at com.sterlingcommerce.woodstock.install.InstallSIBootstrapper.instanciateAndRun(I nstallSIBootstrapper.java:352)
[exec] at com.sterlingcommerce.woodstock.install.InstallSIBootstrapper.instanciateAndRun(I nstallSIBootstrapper.java:356)
[exec] at com.sterlingcommerce.woodstock.install.XAPIWrapper.processXAPI(XAPIWrapper.java: 43)
[exec] at com.sterlingcommerce.woodstock.install.module_loader.ServiceInstall.processXAPID irectory(ServiceInstall.java:1810)
[exec] at com.sterlingcommerce.woodstock.install.module_loader.ServiceInstall.doServiceCom monTasks(ServiceInstall.java:909)
[exec] at com.sterlingcommerce.woodstock.install.module_loader.ServiceInstall.installServi ce(ServiceInstall.java:732)
[exec] at com.sterlingcommerce.woodstock.install.module_loader.ServiceInstall.install(Serv iceInstall.java:304)
[exec] at com.sterlingcommerce.woodstock.install.module_loader.ServiceInstallDriver.doIt(S erviceInsta

Resolving The Problem

The OOM error occurs in the “munge” target of xapiDeployer.xml. This occurs because it attempts to load all the files mentioned in the target into memory.
If the number of backup files that exist in <INSTALL_DIR>/bin, <INSTALL_DIR>/properties and <INSTALL_DIR>/resources are quite huge, then one may see this problem.
The execution of <INSTALL_DIR>/bin/setupfiles.sh creates the backup files. The execution maybe explicit to propagate changes made in <INSTALL_DIR>/properties/sandbox.cfg or implicit (e.g. when an install3rdParty.sh is executed, an EAR is built etc.).
A possible resolution to avoid this problem:
       
  1. Run a periodic job that deletes the backup files generated.
    2.    
  2. Delete all the backup files prior to starting the HF installation.
The files will grow over a period; hence if one does not expect to install HFs frequently, then one should take these precautions to avoid an OOM error.

[{"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

NFX9439

Product Synonym

[<p><b>]Function Area[</b><p>];HF Installation.;[<p><b>]Escalation ID[</b><p>];00139295;00195033;[<p><b>]Severity[</b><p>];Normal

Document Information

Modified date:
16 June 2018

UID

swg21557264

Page Feedback