Community
Participate
Working Groups
When starting my weblogic server installation, I get a timeout message after a certain time (75 seconds) of the server starting up. My application is so big that it always takes more than 75 seconds to start. There should be somtheing in the server definition to configure that timeout to 120 seconds or even more. Some of my team-members have anti-virus software that slow this process down to about 4 mintues to start weblogic... Even after the message, it seems to pick up the right server state after a while. I didn't get that message in 0.7.1. Regression?
FYI, there is a "relative speed" option in the Server preferences, but that may not be enough to cover the large time difference.
I had not noticed that option (I'm guessing that it is the <Server timeout delay> option. The relative mesurement don't mean much to me as I don't know how wether 90 seconds is a <long> time or a <longer> time. I believe this should work for me though unknown for some of my team mebers that take up to 4 minutes (what is "Longer" set to???). Could it not have something like the <Automatically Publish> items... a checkbox that says <warn on server start timeout> and a spinbox for <server timeout (in seconds)> It would have been a "nice to have" if the timeout dialogue referred you to that setting (with a link?) as I was simply getting annoyed.
There is already a request for configurable time out options. We can have a longer time out period for weblogic, this server config is maintained by Rob so I will let him decide. *** This bug has been marked as a duplicate of 121593 ***
Although the WLS timeout value could be increased, I don't know that it would be practical to set the default high enough to cover this particular use case (i.e. a 4 minute startup time). I think it will be preferrable to either get the fix for 121593 or a solution similar to what we had pursued in https://bugs.eclipse.org/bugs/show_bug.cgi?id=104853 (i.e. open a dialog when the timeout expires to give the user the option to continue waiting or cancel the startup) - thoughts?
This bug was moved to 'closed' state, since it is so old is is assumed its dup, invalid, or worksforme resolution is no longer in qustion and the bugzilla needs no further attention. Feel free to re-open, or open a new bug, if this semi-automatic processing was done in error in this case.
