ZOS connector failed to initialize flow
search cancel

ZOS connector failed to initialize flow


Article ID: 191523


Updated On:


CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)


Scenario: When we are running action List Jobs from action pack ca-ra-zos-connector we see that it is immediately getting cancelled with below error from agent log

From Agent Log:

2020-04-10  17:18:33,250 [Communication Msg Processor-14] ERROR (com.nolio.platform.shared.flowcontrol.service.FlowControlService:87) - failed initialize flow for job[590131], jobServerId[590159]

2020-04-10 17:18:33,252 [Communication Msg Processor-14] DEBUG (com.nolio.nimi.appmsg.durability.DurableCommunicationApi:155) - Got new message: papen-app-test.gbbper.priv_158652811063620:payload=[ID:[email protected], from:papen-app-test.gbbper.priv, to:[email protected]_zosmf-nolio-test.gbbper.priv- FlowExecutionEventDto [status=Distribution of execution plan failed., description=null, source=papen-app-test.gbbper.priv, jobServerId=590159, type=FLOW_DISTRIBUTION_ERROR, timestamp=Fri Apr 10 17:18:33 CEST 2020, jobId=590131, eventType=FLOW_EVENT, eventCounter=3]]


Release : 6.4

CA RA ZOS Connector: 1.0.0, 1.1.1SNAPSHOT5 or higher



After review of the logs we found that in agent logs nolio_action_exe.log we can see below error, the below error is self-explanatory that an action is trying to refer a class but can't find the same.

2020-05-22 04:55:55,492 [Communication Msg Processor-12] ERROR (com.nolio.platform.shared.flowcontrol.service.FlowControlService:87) - failed initialize flow for job[327680], jobServerId[327680].

java.lang.NoClassDefFoundError: javax/ws/rs/ProcessingException
 at java.lang.Class.getDeclaredConstructors0(Native Method)
 at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
 at java.lang.Class.getConstructor0(Class.java:3075)


When you installed the Z/OS connector using the installer on the CA Release Automation server, It get installed with below 10 JARS. One connector jar and other 9 are the jars on which connector jar depends on.

During the analysis of the actionsLib folder of NAC, NES and agent we found that some of the dependent jars are missing, which is resulting in the error mentioned above. For ca-ra-zos-connector*.jar to work properly it need the relevant dependent jars to be present, so that it can load required libraries and execute the task. To correct the missing jars, please follow below steps.

1: Create a backup of actionsLib folder of NAC
2: Stop the Release Automation Server (NAC) service
3: Extract the depended 9 jars into actionsLib folder of the NAC (This can be obtained from the existing working instance in your environment or the 1590489387585__zos connector dependency jars.zip attached to the KB). Please make sure the version of dependent jars are compatible to work ca-ra-zos-connector*.jar.
4: Start the NAC service
5: Try to run the action/process. This run will synchronized the missing jars on the NES and respective agents and it will let the action run and not fail on initialization.

Additional Information

In case of any query please feel free to contact CA Release Automation Technical Support.


1590489387585__zos connector dependency jars.zip get_app