Bugzilla – Full Text Bug Listing
| Summary: | All server configurations need timeout options the user can override. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP ServerTools | Reporter: | Scott Delap <scott> | ||||
| Component: | jst.server | Assignee: | Angel Vera <arvera> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | arinfein, daniloesk-eclipse, danny.ju, deboer, eyuen7, gorkem.ercan, gregoire.seguin, leo, paul_galbraith | ||||
| Version: | 1.0 | ||||||
| Target Milestone: | 3.0 M3 | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Scott Delap
Have you tried changing the setting under Window > Preferences > Servers? You can globally change the length of all timeouts based on your computer speed. You mean the slow, medium, fast ( or something like that option? Yep tried that. I'll admit the machine I've been testing things on is a little slow but if you had a robust J2EE server startup that had to initialize clustering, multiple db connections etc, you'd also run into the same issues. A hard X seconds which you could specify 300 or something would be nice. I've also found that clicking the X on the dialog box instead of explicitly saying ok on the timout error will let the server keep going in some cases. That seems like a bug/feature =). (In reply to comment #1) > Have you tried changing the setting under Window > Preferences > Servers? You > can globally change the length of all timeouts based on your computer speed. > Specifying short/normal/long etc. doesn't seem to make any difference at all, at least for a WebLogic 8.1 configuration, the timeout value seems to come only from org.eclipse.jst.server.generic.serverdefinitions_1.0.0/plugin.xml; having this value more easily configurable would be very useful. *** Bug 126950 has been marked as a duplicate of this bug. *** So far (up to JST SDK 1.0.1.v200602130105) I was able to make it work by changing the timeout directly in the plugin.xml, but since JST SDK 1.0.2.v200604280000 that stopped working. No matter what I do, the timeout sticks to the original 75000ms. I tried recreating the server configuration and using a brand new workspace, but nothing worked. Going back to the 1.0.1 version turned everything back to normal. I finally realized that the server timeout preference was no longer being used, and this is being fixed for 1.5.1 and 2.0 via bug 150090. The preference allows you to change the overall startup timeouts from about 1/2 to 2x the standard timeouts, to allow for machine differences. Does that cover the requirements of this bug for your use cases? Should the range be expanded? Or should this bug be used as an enhancement request for specific timeout values per server instance or per server type? (In reply to comment #6) > The preference allows you to change the overall startup timeouts from about 1/2 > to 2x the standard timeouts, to allow for machine differences. Does that cover > the requirements of this bug for your use cases? Basically, no. It would be far more convenient to simply allow for a precise configuration, in seconds. short/long/longer/normal, etc., is not going to have any understandable meaning for most people, forcing them to resort to trial & error to try to reverse engineer the meaning of these terms, and these terms will never cover a broad-enough or precise-enough spectrum. (In reply to comment #6) > The preference allows you to change the overall startup timeouts from about 1/2 > to 2x the standard timeouts, to allow for machine differences. Does that cover > the requirements of this bug for your use cases? Should the range be expanded? > Or should this bug be used as an enhancement request for specific timeout > values per server instance or per server type? > I believe the timeout should be the last one (specific values per server instance). The main reason is because the time necessary to start a server depends on the applications it needs to start, not only on the server type. If a large application or many small applications are installed on a server, the time necessary is *not* relative to the server type. Changing OS from Mac OS to Mac OS X as per bug 185991 Reassigning to Angel since he'll be looking at the timeouts for 3.0. *** Bug 205997 has been marked as a duplicate of this bug. *** Created attachment 80960 [details]
timeout per server enhancement
I have completed this enhancement, and there will now be a start and stop timeout value that users can modify. The settings will be per server
*** Bug 181845 has been marked as a duplicate of this bug. *** Released to the weekly 3.0 M3 build. Thanks Angel! Verified, closing. |