The nolio_dm_all.log on NAC server registers the following error while deployment:
[StageExecutorTask-1234] ERROR (com.nolio.releasecenter.services.release.execution.engine.ArtifactsEngineImpl:354)
- id to load is required for loading
java.lang.IllegalArgumentException: id to load is required for loading
The nolio_all.log from the retrieval agent shows the error:
[Communication Msg Processor-12] INFO (com.nolio.platform.shared.communication.services.artifacts.ArtifactCommunicationService:123)
- Artifact download Task Failed java.lang.OutOfMemoryError: Java heap space
Release Automation - 6.9.0
The default allocated memory is not enough for the retrieval agent to download large artifact.
Immediate approach to address the problem is increasing heap memory on retrieval agents.
Follow these steps:
Stop the Nolio Agent service.
wrapper.conf (retrieval agent):
=========================
Uncomment the lines and change the values.
From:
...
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3
# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64
...
To:
...
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=512
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024
...
Then start the Nolio Agent service.
This issue is fixed in the next minor update for Nolio 6.9, specifically in 6.9.1:
See this reference:
35658679 Artifact file size causes java OutOfMemory errors.
So as a long term solution the best way is to plan the minor upgrade to the latest available 6.9.x (currently it's 6.9.2).