NB 200728051800: Servers/Options
Startup TimeOut value when changed to a small value (gave 10 sec) less than the
smallest time-value needed to start the server instance, if the end-user stops
and starts the server instance again, he will be confused as:
+++ an Error window form IDE pops up telling him "Server Startup had timed out"
+++ while in the Output-server he will see the progress of start and
at the end, the server is started with success
+++ after closing the Error window, the server node status is coherrent with the
IDE errro, but not coherrent with the real server status.
+++ Refresh Action on the node updates the status to Started.
I think a small improvement of this new feature is welcome: like define the
range of allowed input-values specially for the low side.
May be we can implement something like: new value >= default value even if Adhoc
There really isn't a way to compute what the smallest time should be... So this
is really a request for the IDE to end up in a consistent state...