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:-)
> 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
>