Can't connect to debugged process:Could not connect to server

[xiaohong yu]

when i build the .java file ,i find it is useful ,but when i restart the eclipse ,and then do the same thing ,it is no use ,and there is the question:Can't connect to debugged process:Could not connect to server.
java.io.IOException: Could not connect to server.
gov.sandia.jess.debug.model.JessDebugTarget.<init>(JessDebugTarget.java:57)
gov.sandia.jess.debug.launching.JessLaunchConfigurationDelegate.launch(JessLaunchConfigurationDelegate.java:67)
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:569)
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:788)
org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:955)
org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

[Ernest Friedman-Hill]

Like all Eclipse debuggers, the Jess debugger starts a new process to run the debugged program. You'll see this message if, ten seconds after launching a JVM to run your Jess program, the second JVM still hasn't started listening for commands from the debugger. Each debugged process uses its own separate ports for listening, so the problem is not that the ports are colliding.

I'm not sure what restarting Eclipse has to do with anything, or for that matter, what compiling has to do with anything (I suspect you say "compile" when you mean "run"). Maybe you have a slow machine, or a machine with little memory, and it's just not capable of running Eclipse plus two more JVM processes all at the same time?

[xiaohong yu]

thank u very much .i see it