WSAD Debug server mode will not compile JSPs

[Einstein47]

I really love WSAD 5.1.1 - especially the debug server mode which allows me to step through any servlet or JSP. And it was working perfectly for me until last week.

Now, however, when I try to run in debug mode I can step through the servlet, but as soon as I call the JSP - WSAD seems to freeze. I get nothing.

I have tried uninstalling and reinstalling, to no avail. I did get it working once after, but the steps were like (break the local test server config, WSAD prompts to fix the server, then restart in debug mode). But since I can't remember what I did to "break" there server configuration I can't repeat my steps. breaking a configuration is NOT a good work-around..

So I was just wondering if someone might know what I should look at to see why debug fails to compile my JSPs. Other programmers on my team do not have this issue. I'm the lucky one.

Thanks in advance.

Einstein47
("The pure and simple truth is rarely pure and never simple." - Oscar Wilde)

 

[Einstein47]

If anyone cares - I found that when I disabled the "hot recompile" of the classes, then the debug mode will work. This is odd, since the error was happening on compiling the JSPs and they will get recompiled even "hot".

Whatever, I really liked being able to make a change and the server recognizing the modification, but I'll live without it so I can have debug back.

You enable/disable this option by a checkbox on the first tab of the server definition. Good luck to anyone else that may encounter this issue.

Einstein47
(Trouble is a sieve through which we sift our acquaintances. Those too big to pass through are our friends. - Arlene Francis)

 

[Einstein47]

Ok - if anyone searches for this and needs help, I have the real fix and why.

If you are having trouble getting the debugger to connect to your application, you may need to increase your Java debug timeout settings. To determine if you are having this problem, check your <workspace>\.metadata\.log file for the existence of org.eclipse.jdi.TimeoutException messages. To increase the Java timeout settings, choose [red]Window > Preferences[/red] from the workbench menu bar. Expand the Java node and click Debug. In the Debug preference page, [red]increase both of the Communication timeouts (Debugger timeout (ms) and Launch timeout (ms)[/red] - it is recommended that you at least double the default values for these two fields). If the timeout settings are not increased, the debugger will appear to hang when you perform a debug on server.

Einstein47
(Some people make things happen. Some people watch things happen. Some people wonder what happened. - Unknown)