cancel
Showing results for 
Search instead for 
Did you mean: 

SDM takes too LONG a time to deply - Suddenly.

Former Member
0 Kudos

A small model with 3 views that calls 3 different Bapi was deployed as WD for Java .

The deployment and run used to take 30 to 40 sec.

Suddently, it jumped to 5 minutes. I thought few objects were locked.

I use NWDS to deploy. I am not going through NWDI / CMS

-


07/12/20 15:02:29 - Start updating EAR file...

07/12/20 15:02:29 - start-up mode is lazy

07/12/20 15:02:29 - EAR file updated successfully for 6ms.

07/12/20 15:02:29 - Start updating...

07/12/20 15:02:30 - EAR file uploaded to server for 175ms.

07/12/20 15:07:30 - Successfully updated. Update took 300435ms.

07/12/20 15:07:30 - Deploy Service status:

07/12/20 15:07:30 - Application : local/approvalStandalone

07/12/20 15:07:30 -

07/12/20 15:07:30 - local/approvalStandalone - WEBDYNPRO

07/12/20 15:07:30 - ***********************************************************

Dec 20, 2007 3:07:30 PM Info: End of log messages of the target system.

Dec 20, 2007 3:07:30 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

-


Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Restart helped. But there is no valid reason, why suddenly the deployment time jumped from 30 sec to 5 min.

Only 2 developers in the machine. The other developer was not working with SDM

Former Member
0 Kudos

Hi Thinkaran,

sounds like it is time for server restart. I had the same effect multiple times and that worked for me in most cases.

regards,

Christian