WAS- Start Managed Server(s) action error: WebSphere servers are not started

Products

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

Issue/Introduction

WAS- Start Managed Server(s) action fails in starting WebSphere server. Log contains error similar to:

 

2017-09-21 13:26:25,159 [job-1969715-jobServer-1974201-5:Start WAS Server(P7835127.F7835275.E7835472.E7835468.E7835283)] DEBUG (com.nolio.platform.shared.communication.CommunicationNetwork:414) - Sending internal message:[ID:[email protected], from:xxxxxxxxxxx.europe.intranet, to:[email protected]_xxxxxxxxxxx.be.extranet- StepExecutionEventDto [result=Step Result: false - Failed to start target servers / clusters.<BR><BR>Servers: <BR>N_xxxxxxxxxxx,SLADMINISTRATION_Server : Failed starting server [node=N_xxxxxxxxxxx, server=SLADMINISTRATION_Server]. Inner Error: ADMC0009E: The system failed to make the SOAP RPC call: invoke <BR>, hostIp=xxxxxxxxxxx.europe.intranet, jobId=1969715, envServerId=1974201, timestamp=Thu Sep 21 13:26:25 CEST 2017, state=FINISHED, stepId=P7835127.F7835275.E7835472.E7835468.E7835283, stepTitle=Start WAS Server, startDate=Thu Sep 21 13:22:53 CEST 2017, stopDate=Thu Sep 21 13:26:25 CEST 2017, eventCounter=782]]

Environment

Release Automation 6.x agent on Linux/Unix

Cause

Action is configured like this:

 

<Please see attached file for image>

 

Timeout is exceeeded even though it is set to unlimited in the action parameters.

Resolution

Follow instructions as listed in http://www-01.ibm.com/support/docview.wss?uid=swg21308292

The timeout in the action only designates how long the action itself is allowed to wait until the start operation finishes. 
But the timeout as designated by com.ibm.SOAP.requestTimeout is the time WebSphere itself allows the request to take. 
So just leave the timeout in the action set to 0 but modify the com.ibm.SOAP.requestTimeout to 6000 within was_profile_root/properties/soap.client.properties.