Deployment blocked at every end of step. Failed to reporting module artifacts deployment
search cancel

Deployment blocked at every end of step. Failed to reporting module artifacts deployment

book

Article ID: 415132

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

Execution of a deployment is blocked at end of every steps.

With JMX command the blocked job could be deleted, the next step is executed but is blocked again at the end of step execution.

 

In the NAC log there are lines like this :

2025-09-02T23:42:26.772-04:00 [eventsProcessingHandler[job:<JOBID>]-1] INFO  (com.nolio.releasecenter.services.release.execution.engine.StageExecutionTransitionManager:187) - reporting module [<STEP NAME>] artifacts deployment at the end of it's run
2025-09-02T23:42:26.832-04:00 [eventsProcessingHandler[job:<JOBID>]-1] ERROR (com.nolio.releasecenter.services.release.execution.engine.StageExecutionTransitionManager:191) - Failed to reporting module artifacts deployment. moduleId[<MODULEID>]
java.lang.NullPointerException: null
 at com.nolio.platform.server.dataservices.services.model.ProcessesManagementServiceImpl.lambda$collectComponentArtifactTypes$2(ProcessesManagementServiceImpl.java:983) ~[ra-business-logic-services-6.8.0.jar:?]
 at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183) ~[?:1.8.0_332]
 at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) ~[?:1.8.0_332]
 at java.util.Iterator.forEachRemaining(Iterator.java:116) ~[?:1.8.0_332]
 at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) ~[?:1.8.0_332]
 at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) ~[?:1.8.0_332]
 at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) ~[?:1.8.0_332]
 at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150) ~[?:1.8.0_332]
 at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173) ~[?:1.8.0_332]
 at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_332]
 at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485) ~[?:1.8.0_332]
 at com.nolio.platform.server.dataservices.services.model.ProcessesManagementServiceImpl.collectComponentArtifactTypes(ProcessesManagementServiceImpl.java:978) ~[ra-business-logic-services-6.8.0.jar:?]
 at com.nolio.platform.server.dataservices.services.model.ProcessesManagementServiceImpl.collectServerTypesArtifactTypes(ProcessesManagementServiceImpl.java:959) ~[ra-business-logic-services-6.8.0.jar:?]

Environment

Release Automation 6.8.0

Resolution

Root cause was not known. A workaround is to restart the Release Automation service on the NAC.
After the restart, the deployment could be executed successfully.

Additional Information

If problem occurs and root cause must be found a case at Broadcom support could be opened with following logs :

  1.  Enable stack traces logging on the NAC side calling the JMX method setMinimumCpuPercentageForThreadDump  for the type=PerfMonitor manager. Zero value should be specified as the minCpuForThreadDump parameter.
    Default login/password for JMX is nolio/nolio

    http://localhost:20203/mbean?objectname=noliocenter%3Atype%3DPerfMonitor

    Component: MBean noliocenter:type=PerfMonitor
    Operation: setMinimumCpuPercentageForThreadDump
    Parameter: minCpuForThreadDump set this value to 0.
    click on Invoke



  2. Reproduce the problem and attach the full directory logs of NAC  (ex: C:\Program Files\CA\ReleaseAutomationServer\logs)
Powered by Wolken Software