Bug 105375 - Servers/Options Startup TimeOut new value range missing
Servers/Options Startup TimeOut new value range missing
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: Code
6.x
All All
: P2 (vote)
: 6.x
Assigned To: Vince Kraemer
issues@serverplugins
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-01 10:31 UTC by nouar38
Modified: 2007-07-26 19:32 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nouar38 2007-06-01 10:31:21 UTC
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
choosen.
Comment 1 Vince Kraemer 2007-06-06 15:35:04 UTC
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...


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo