deployment engine terminated due to heap storage

Technote (troubleshooting)


Problem(Abstract)

Deployment engine ended after customer submits multiple concurrent provisioning requests.

Symptom

Deployment engine terminated due to lack of heap storage when customer submits multiple provisioning requests concurrently. The Deployment engine log shows the following exception:

.

2010-10-28 09:51:52,231 ERROR [Deployment Request 119917]

(DeploymentWorker.java:588) engine.DeploymentWorker: java.lang.OutOfMemoryError

.



Resolving the problem

In order to raise the limit of Java environment memory, please enlarge the memory available for the java process by editing the script run-deploymentengine.sh/cmd. Change the amount of memory at the line:

".../java" -Xrs -Xms256m -Xmx1024m

and restart the TPM.

Please note that there is always an upper limit to the available of memory. There is no recommendation of this setting. Customer may have to tune the amount of memory increased and the number of concurrent processes to stay within the capacity of the system.

For reference, customers can review section "Considerations for running concurrent jobs" in the TPM Workflow Guide for specific considerations for supporting concurrent jobs.

.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Provisioning Manager for Software

Software version:

5.1.1, 7.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1455023

Modified date:

2013-01-26

Translate my page

Machine Translation

Content navigation