The question is a timeout is not easily determined. For example, if
you multiple applications deployed, start-domain or java -jar won't
return until all applications are loaded/initialized. I am not sure
we can say 90 seconds are enough to load an arbitrary number of
deployed applications. Life-cycle kind of services may have
an impact on startup as well.
Asadmin start-domain command implementation made a choice to wait for
90 seconds and then give up determining what's up with the server,
rather than waiting forever. The current choice makes asadmin terminate
and leaves the startup unaffected. I don't think there is anything
viciously wrong with that choice. In other words, I can definitely
provide a configurable timeout, but it does not buy user a lot.
-Kedar
Ludovic Champenois wrote:
> Kedar Mhaswade wrote:
>>
>>
>> Ludovic Champenois wrote:
>>> Ajit Kamble wrote:
>>>> Hi Kedar ,
>>>>
>>>> Thanks for the answer. I will file an RFE.
>>>>
>>> On the other end, doing 90 seconds of setup for an app running on top
>>> of V3 seems a bug as well, no?
>>> I boot opensolaris is less than 90 seconds:-)
>>
>> You mean a bug in the app(s), or that in app server?
> My first guess would be in the app itself... OR maybe it is time to
> profile the entire area both from the App server side, and this web app
> side and get the repartition numbers. 90 seconds is a lot imo.
>
> Ludo
>> I think we made a decision
>> that server startup won't return without initializing (loading) all
>> the deployed
>> apps and it is difficult to come up with a time-out for that to
>> complete. It
>> will take what it needs, which is safe, I guess.
>>
>>
>> -Kedar
>>
>>>
>>>> Thanks
>>>> Ajit
>>>>
>>>> Kedar Mhaswade wrote:
>>>>> Ajit,
>>>>>
>>>>> The timeout is not configurable at the moment. And like the message
>>>>> says,
>>>>> the startup may *not* be aborted. It's just that asadmin program gives
>>>>> up after 90 seconds. The server and all its applications will
>>>>> eventually
>>>>> come up. If you think asadmin should wait indefinitely or the timeout
>>>>> should be configurable, please file an RFE.
>>>>>
>>>>> But please note that this does not relate to server being up.
>>>>>
>>>>> Thanks,
>>>>> Kedar
>>>>>
>>>>> Ajit Kamble wrote:
>>>>>> Hi ,
>>>>>>
>>>>>> After executing ./asadmin start-domain in GFv3 it ideally waits
>>>>>> for 90 secs which is predefined. But for project websynergy we
>>>>>> want this to be more by default ( around 2 mins) otherwise below
>>>>>> message is on the terminal which is misleading.
>>>>>>
>>>>>> /asadmin start-domain
>>>>>> Domain (domain1) did not respond in 90 seconds. It means it is
>>>>>> still coming up
>>>>>> or it has failed to come up. Check server.log for details.
>>>>>>
>>>>>> So, wanted to know the location where it is configurable ?
>>>>>>
>>>>>> Thanks
>>>>>> Ajit
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>>>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>