[20040111]
The current functionality is following:
When user runs the IDE and opens popup menu on a
server instance node there is 'Start / Stop
Server' action. Performing this action user will
get a dialog which allows to run the server. After
the server is started the popup menu exposes 'Stop
Server' action instead of the 'Start / Stop
Server'. This is behaviour is fine. Unfortunatelly
when user stops the server the action 'Stop' is
replaced by action 'Start / Stop' again. This
seems to me to be little bit confusing since we
know that we have just stopped it.

I suggest having two actions on the server
instance node:
Start Server
Stop Server

They are enabled/disabled according to the server
state. To avoid performance problems during popup
creation there are suggested two solutions:
1) let the actions enabled both for the first time
when user starts the IDE (we do not know if the
server is running or not)
2) create a background thread when the IDE is
started to test if the server is running or not.
Create a semapore for each server. This would
eliminate the delays during creation of the actions.

Since we check the server status for the first
time we can easily enable and disable the both
actions. The 'Start Server' action is disabled
(and 'Stop Server' action enabled) when the thread
which runs the server process is started. 
When the thread finishes do the same conversely.

The only risk of this model is that someone runs
the server externally on the some port after we
stopped our internall server instance. IMO this
case is very rare so it is not worth of an
additional test (and the weird 'Start / Stop
Server' action)