cancel
Showing results for 
Search instead for 
Did you mean: 

SDM deployment of webdynpro takes a LONG time..

Former Member
0 Kudos
86

Pardon me if this is not the right place to post. I am also posting it in webdynpro Java.

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.

-


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

I followed the thread Atul suggested. the machine is very powerful with lot of memory. Only 2 developers. At this instance, only one was working deploying simple example models.

It has nothing to do with Jco as even the examples took a long time.

Need to close this thread as there is no valid reason.

Restarting the server fixes the problem. But it is not a good explanation, is it not?

Former Member
0 Kudos

You can close the thread but restarting the server is not a solution sir.

I will request you to check with the network guys as well about the bandwith also.

Alternatively just try installing NWDS on the portal server and try deploying some small application from there only..just to check it if it takes less time or the same.

regards

Atul Shrivastava

Former Member
0 Kudos

Hi,

Seems you are using a single Jco Connection to connect all the BAPIs.

If this is the case, simply check the time out parameters in hte Jco Connection.

secondly try deploying a simple application just to check if the issue is application specific or related to SDM.

hope this helps!

regards

Atul Shrivastava

PS:Award points if helpful.

Former Member
0 Kudos

Atul,

Same problem. Even a small webdynpro table example that does not have any Jco, does the same.

Former Member
0 Kudos

Try following this thread:

regards

Atul Shrivastava

PS:Award points for helpful answer.