Show TOC

Background documentationError During Deployment Locate this document in the navigation structure

 

Problem 1: Out of Memory

JSPM cannot deploy all components. The deployment of at least one of the components that you selected has finished either with status DEPLOYED WITH ERROR or with status NOT DEPLOYED.

Possible Reasons

Check if the /usr/sap/<SID>/<application server instance name>/j2ee/cluster/<Server process>/log/defaultTrace.<xx>.trc file contains an OutOfMemory exception. Such an exception occurs if not enough AS Java memory is available.

Solution

On all operating systems - using the Config Tool, set the heap size and permanent space Java parameters as described in SAP Note 723909.

Caution Caution

On Linux on AMD64/EM64T Linux - set the Java parameters as described in SAP Note 861215.

End of the caution.

On Microsoft Windows - get the SAP Address Space Viewer and rebase the DLLs as described in SAP Note 129813 and SAP Note 736462.

For more information about troubleshooting the AS Java, see SAP Note 764417.

For more information about setting the Java parameters, see Layout, Menus, and Features of the Config Tool.

Problem 2: JSPM Hangs On During Deployment

JSPM hangs on during deployment. If your database is MaxDB, the deployment may continue longer than expected (the maximum expected deployment time is about 3 hours).

Possible Reason 1

If your database is MaxDB, the logs may be full.

Solution 1

If your database is MaxDB, we recommend that you set the overwrite mode for the log area. For more information, see Changing Log Settings

Possible Reason 2

If your database is MaxDB, the parameter MAXUSERTASKS may have insufficient value.

Solution 2

If your database is MaxDB, we recommend that you set the parameter MAXUSERTASKS to at least 50.

For more information about MAXUSERTASKS see General Database Parameters and SAP Note 757914.

For more information about changing database parameters see Changing Database Parameters.