|Generic External Server says shutdown failed before stop script has returned [message #231099]
||Wed, 06 May 2009 11:15
| Anders Olsson
Registered: July 2009
I've defined a Server Adapter with
Starting the server leaves a process running for the lifetime of the
Stopping the server runs the same script with a stop parameter which
signals the running server process to shut down.
My problem is that as soon as I press stop on the running server I get an
error dialog with the name "Problem Occurred", saying:
'Stopping <Server name> at <Server IP>' has encountered a problem. Server
<Server name> at <Server IP> failed to stop.
This error comes from line 2942 in
org.eclipse.wst.server.core.internal.Server (in 3.0.4). And is created
because the server is still identified as running.
The script takes a bit of time to finish, and usually the stop-script ends
before the server process (though I could change that order if it would
help). I've set the Stop timeout of the server to 60 seconds, which is
I cannot see where the problem is in the WST/JST code, but is seems there
is a problem that stops the WST/JST code from waiting for the command to
return, before passing it's judgment on whether or not it was successful.
I've got the Eclipse Web Tools Platform book, but how this is supposed to
work for Externally launched servers.
Worth mentioning is that the server is actually running on a remote system
and the start and stop scripts are just local placeholders which signal
the remote system).
Can someone enlighten me what I might be missing in the logic I'm
currently using. This should be such a common use, that I'm hesitant to
file a bug report, because the problem is likely in my end.
Powered by FUDForum
. Page generated in 0.01959 seconds