> You may be seeing the same result (i.e., the launch apparently failing) but
> not for the same reason as Rankin. The JDE is not getting a response from
> the debugger after commanding it to launch your test app. I see nothing
> obviously wrong with your setup. One possibility is that javaw takes a long
> time to start on your system. If the debugger does not respond to a command
> within ten seconds, the JDE assumes something is wrong and gives up. If in
> fact the problem is slow startup, you can fix it be customizing
> jde-bug-debugger-command-timeout. Try setting the timeout factor to a large
> value, say 20 seconds.
I tried setting it as high as 60 seconds and got the exact same result. I did a
bit of exploring through the JDE java code and it seems to make it all the way
down to jde.debugger.Application.getConnector(). The call to
com.sun.jdi.Bootstrap.virtualMachineManager() never returns. If I call
Bootstrap.virtualMachineManager() from a test application, it returns an
instance of com.sun.tools.jdi.VirtualMachineManagerImpl right away. If anyone
has suggestions, I'd be happy to hear them because I'm out of ideas at this
point.
Mike Burr
[EMAIL PROTECTED]
"...and when tweetle beetles battle with paddles in a puddle, they call it a
tweetle beetle puddle paddle battle." - Dr. Seuss
