CMS Application - Delivery - Set as current version - Deploy source code - Fatal Error - Not able to set as current version after rejecting already accepted version

This page outlines the issue of not able to set as current version after rejecting the package which is already accepted.

Refer the below error message:

Error:  DETAILPreparing to run Importer with process JVM to 1G
            DETAILDefining Log server thread as a new logging context without any writers
            DETAILError occurred during initialization of VM
            DETAILCould not reserve enough space for object heap 

1. Deliver the package from DMT.

2. Set as current version.

3. Delivery is rejected.

4. Delivery is accepted and set as current version.

5. Set as current version will crash.

The issue here is the system is unable to allocate the requested 1 GB of memory and hence the JVM aborts and set as current version fails with  the above mentioned error.

The solution is to counter this memory problem, for this we have to allocate more than the required memory for the JVM.

1. So ensure that at least 2 GB of RAM is available while running the set as current version.
   Also
2. Make sure that you do not have any static memory settings, Xmx runtime parameter set which prevents in allotting the required memory for JVM.
   1. If yes, then you need to clear the Xmx runtime parameter to make it empty. See the attached below screenshot which points to the Xmx runtime parameter for Java settings.
      
      

Unable to set as current version in CAST- MS.

Ticket # 4287