eclipse plugin needs improved network server process handling
-------------------------------------------------------------
Key: DERBY-314
URL: http://issues.apache.org/jira/browse/DERBY-314
Project: Derby
Type: Bug
Components: Tools
Versions: 10.0.2.0
Environment: windows, eclipse 301, jdk142
Reporter: Myrna van Lunteren
Priority: Minor
The eclipse plugin allows you to create multiple network server processes
within the same project through a gap in the checking mechanism, but you can't
close all those you create that way from within eclipse.
To duplicate do the following:
- setup the plugin and apply the eclipse nature to a project
- start network server on the default port.
- switch the port number using the derby preferences e.g. to 1528
- go to the derby task - you see that the networkserver start/stop is a toggle,
and because last time you started a networkserver process, it is now on 'stop'.
Run the 'stop Networkserver. This will fail, because network server is not
running on port 1528, so cannot be stopped.
The toggle will now go back to 'start'.
- start networkserver on port 1528.
- trying this 'trick' in reverse - i.e. for the start - does not work, if the
start fails, the toggle remains on 'start'.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
