cancel
Showing results for 
Search instead for 
Did you mean: 

Deployment while Server is in "debugging" mode?

Former Member
0 Kudos

Hi Group,

when you debug - how do you test your new changes?

When server is in state "debugging" i'm not able to deploy (deployment "hangs" till i "release from debugging")

So to debug the new CHANGES takes a lot of time..

When i set the flag "create and deploy archive" and press "debug" i get the exception "no connection to remote VM".

(Without the flag debugging works fine..)

Any ideas?

Thanks alot!

Simon

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Simon

It is strange that when the server is "debug ready" you are not able to deploy. This is usually not the case. How about

->switching off "create and deploy archive"

->deploy through the deploy function

->then launch debugging

Regards

Pran

Answers (1)

Answers (1)

former_member182372
Active Contributor
0 Kudos

Hi Simon,

I prefer not Web Dynpro Application debug profile type but following way:

1) Build and deploy new archive of wd project.

2) Create Remote Java Application debug profile. Specify your host, port and project. Set breakpoints etc.

3) Start debug

4) Select appropriate WD application and from context menu select Run

5) Debug. Find a bug. Stop debugging.

6) Make changes and repeat steps 1, 3, 4

Best regards, Maksim Rashchynski.

Former Member
0 Kudos

Hi Maksim,

Thank you very much for your reply, interesting approach!

But what exactly is the benefit?

In your solution you also have to stop debugging (which means restart of node) to deploy again, or not?

Thanks,

Simon

former_member182372
Active Contributor
0 Kudos

Hello Simon,

Stopping is necessary because you need to synch running code and code in NWDS. Without stopping you can get inconsistemcy between running code and source code. The benefit is that you have 2 options to launch your application - from studio and from url, so it seems to be more flexible. Again, it is my personal opinion.

Best regards, Maksim Rashchynski.

Former Member
0 Kudos

OK - Thanks all - you are right,

it seems to be as it is.

(Its just a little time-consuming - but well...)

I think it makes sense, to stop debugging (because of staying in synch) - but it's das, that the node has to be started then. This is what takes the time...