cancel
Showing results for 
Search instead for 
Did you mean: 

NWDS - WebDynpro Debugging issue

Former Member
0 Kudos

Hi,

I am using NWDS to Debug Webdynpro DCs.

I am following the correct procedure to debug. But, the strange thing is that on <b>some occasions</b>, when I try to debug the application (all debug process correctly followed), I get the the following error:

<b>Exception occurred during launch

Reason:

Failed to connect to remote VM. Connection refused.</b>

Sometimes, when I restart the server again, this problem goes away. Other users are also debugging on the same server. But, I debug only after ensuring that other users are disconnected.

This also happens when no other users debug on the server.

Can anyone throw some light on this issue.

Thanks in advance.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi sandeep

This type of error can occur only when

some one is already connected or ur specified port is wrong. since you have taken care of these two things, the possible cause of this error might be due to some problem in network connection. if possible check out with your basics guys.

check these links for more information........

/thread/205381 [original link is broken]

Thanks.....

Answers (3)

Answers (3)

Former Member
0 Kudos

When i made the other user DISCONNECT the session the problem disappeared.

Still, there are times, when it gets stuck and i haven't been able to figure it out.

Former Member
0 Kudos

Hi,

You will get this error mostly under one or more of the following conditions:

1...some other user is debugging on the same J2EE engine

2...some other user is currently deploying his/her application/DC project

3...the SDM of your J2EE engine has stopped.(You can confirm this by looking in the <i>J2EE engine view</i>)...This is needed if you hav checked the "deploy new archive and run" option

4...The J2EE server has been stopped

I hope this points you in the right direction.

Regards,.

Hanoz

Joseph_BERTHE
Active Contributor
0 Kudos

Hi,

I faced to the same problem, and my solution was to restar only the SDM (it is much more faster than restarting all the server).

But I don't know why it goes like this. My assumption was network connection problem.

regards