Skip to Content
author's profile photo
Former Member

Web Dynpro Java Debugger is hanging and stuck

Posted on Sep 17, 2008 at 01:52 AM 14 Views

Hello! All

I just install a new NWDS 7.0 sp 13 running on Window XP.

My installation is successful. I create a helloworld DC WD application. I deploy to a central J2EE engine NW 7.0 SP13. I can run the application successful after the deployment.

When I try to test the debugger by putting a break point and run the debugger. The debugger is hanging. I have turn on the server0 debugger mode ON. My debugger port is the same as default 50021. I don't know why my debugger is hanging everytime I try to debug. I have to go to task manager to kill my webdynpro application and run the IDE again.

Note: My debugger is hang when i click the debug button. There is popup with progress bar trying to establishing connection...

Does anyone experience this issue and has a fix for it? please share. Thank you very much.

UI Web Dynpro Java
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • author's profile photo
    Former Member
    Posted on Sep 17, 2008 at 03:22 AM

    while you click the debug window and the pop up show up, try de - selecting the option "create and deploy archive" and see what happens,

    Thanks,

    GLM

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Sep 17, 2008 at 04:36 AM

    Hi Khanh

    Try to reconfigure your application in debugg mode with selecting

    "create and deploy archive" in debugg tab also check or select your

    J2ee Enging-->Instance.

    Thanks

    Anup

    Add comment
    10|10000 characters needed characters exceeded

    • Michael Voss Nandor Gastanek
      May 05, 2011 at 12:50 PM

      Although it might be a little late to reply to this thread...

      If the connection fails, the server process likely is reserved for another debug session. This may be one you started yourself that did not terminate correctly. Try restarting the server process ("Restart process" from J2EE Engine view) and start another debugging session then.