ONLINE DEPLOY timeout 300s issue

[Former Member]

Hi, I am a newbie.  I am not sure whether to raise the problem here.

Currently, I am upgrading SolMan 7.1 from SP5 to SP10 with SUM SP09.

At the phase of execution, it did j2ee offline and online deployment.

When proceeding the online deployment, it started dispatcher and server0 for the online deployment.

However, there was a timeout 300s, which caused the first deployment failed.

Jan 21, 2014 6:39:30 AM  Info: SDA to be deployed: /usr/sap/SM3/DVEBMGS00/SDM/root/origin/com.adobe/DocumentServicesLicenseManager/Adobe Sys

tems/6/802.20100226020329.645702/adobe-DocumentServicesLicenseManager.ear

Jan 21, 2014 6:39:30 AM  Info: Software type of SDA: J2EE

Jan 21, 2014 6:39:30 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Jan 21, 2014 6:39:31 AM  Info: Starting cluster instance processes.

Jan 21, 2014 6:39:31 AM  Info: Starting the instance JC_ssma01_SM3_00 running on host ssma01

Jan 21, 2014 6:44:31 AM  Error: An error occured in JStartup Framework: The instance with instance name 'JC_ssma01_SM3_00

     ' did not respond within 300 s. Throwable: com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl Throwable message: The ins

tance with instance name 'JC_ssma01_SM3_00                        ' did not respond within 300 s.

Jan 21, 2014 6:44:31 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Jan 21, 2014 6:44:31 AM  Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20100226020

329.645702'/'6', grouped by :

SDM could not start the J2EE cluster on the host ssma01! The online deployment is terminated.

The instance with instance name 'JC_ssma01_SM3_00                        ' did not respond within 300 s.

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTE

R)

....

....

....

Jan 21, 2014 8:12:50 AM  Info: Starting to save the repository

Jan 21, 2014 8:12:51 AM  Info: Finished saving the repository for 837 ms.

Jan 21, 2014 8:12:51 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Jan 21, 2014 8:12:51 AM  Error: ---------------- At least one of the Deployments failed ---------------

Jan 21, 2014 8:13:18 AM  Info: Summarizing the deployment results:

Jan 21, 2014 8:13:18 AM  Error: Aborted: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/ADSSAP13_0-10006479.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/BIMMR13_0-10006493.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/BIUDI13_0-10006481.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/CAF13_0-10006486.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/CAFUM13_0-10006488.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/ETPRJSCHEDULER33P_92-20007176.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/ISAGENT24_0-20006926.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/ISAGENTJ510_0-10010975.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/JSPM13_0-10006505.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/KMKWJIKS13_0-10006512.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/LMSERVICE10_0-20006622.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/LMTOOLS13_0-10006642.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/SWLIFECYCL13_0-10006668.SCA

Jan 21, 2014 8:13:18 AM  Info: OK: /usr/sap/trans/newsrc/solman71/sp10/51047130/DATA/UMEADMIN13_0-10006669.SCA

Jan 21, 2014 8:13:18 AM  Error: Processing error. Return code: 4

The above show that due to the timeout, the first one could not be deployed successfully.  I already searched sapnotes, like sdm to add parameter j2eeenginestartstop  timeoutmillisec=1800000 and visual admin to extend timeout on dispatcher and server0, but in vain.

Would you please advise any ways to extend 300s timeout longer such that it could give sufficient time to have dispatcher and server0 ready.

Best Wishes,

Michael

[Former Member · Accepted solution]

Fixed.

I temporarily removed /etc/resolv.conf in AIX.  The startup of dispatcher was within 90s.