CMS Application - Delivery - Set as current version - End of set as current version - Fatal Error - Java Heap Space
Description
When setting a delivery as a current version in CAST-MS, the operation fails with the message “Java Heap Space” as shown in the screenshot below:

Observed in CAST AIP
| Release | Yes/No |
|---|---|
| 8.3.x | ✅ |
Observed on RDBMS
| RDBMS | Yes/No |
|---|---|
| CSS | ✅ |
Step by Step Scenario
Below is the step-by-step scenario leading to the problem:
- Package and deliver code in the Delivery Manager Tool (DMT)
- Try to set as current version in CAST-MS
Impact of the Problem
The impact of the problem on the analysis or the dashboard is: No delivery and therefore no dashboard results.
Action Plan
The problem in this case was due to an application that contained literately several thousand of project files (.vcproj, .vcporjx, etc….), causing a huge number of discovered analysis units.
To fix the problem, proceed with one of the following approaches:
- Make sure that you are following the hardware requirements for CAST. For CAST 8.2, this can be seen in the documentation here: Deployment - sizing
- Separate the code into smaller applications instead of having all of the files in one extremely large application.
- Disable the discovery of the technology that is involved in the project discovery (if the project files are .vcproj, disable the C++ file discoverer) by adjusting the package configuration settings and setup the analysis units manually instead. Please see the following documentation on this: Package Configuration tab and Analysis Unit editor
Notes/comments
Ticket # 7281
Related Pages