Hi Cay,
This is a good thread of discussion. Thanks for leading it, and also
thanks to Wouter, Sankar, Sherry, Kedar, Bill, Byron jump
in to share your thoughts. I think combine the suggestion #1 and #2 may
be a good solution.
Cay, how about you log an issue on this to put in your suggestion.
Just to have some fun, today when I close my eye, I see all this
................................................... :-)
Have a happy FishCAT weekend Cay and every one !
Judy
Cay Horstmann wrote:
> Never mind the dots. They are just a symptom. What ticked me off was
> that those dots were filling up my screen INSTEAD OF telling me what
> might be wrong.
>
> Suggestion #1. Do the Microsoft progress bar thing and have the rate
> of dots decrease, so that they don't stupidly fill up the whole screen
> Suggestion #2. Show a tip after a minute or so of waiting to run with
> --verbose.
>
> But really, the problem is with "if your domain configuration is
> broken in certain ways, you can be left in a situation where it won't
> fully start, won't die, and the start-domain command is left waiting
> for a very long time". Then please tell me in which way my domain
> configuration is broken.
>
> Bill Shannon wrote:
>> You know, you just can't win this game! :-)
>>
>> For something that takes an indeterminate and variable time to occur,
>> it's frustrating to have it just sit there doing nothing while you
>> wonder what going on. stop-domain is one such function and it has
>> printed the dots for quite some time. Someone filed a bug saying
>> that start-domain should do the same, which seemed like a reasonable
>> request.
>>
>> Separately, someone complained that start-domain would give up waiting
>> too soon if you had a domain with lots and lots of applications, so we
>> extended the time it would wait before giving up, while also improving
>> it to better detect when the domain fails to start quickly.
>>
>> In the end, if your domain configuration is broken in certain ways, you
>> can be left in a situation where it won't fully start, won't die, and
>> the start-domain command is left waiting for a very long time.
>>
>> If you prefer start-domain to sit quietly waiting, use --terse or
>> AS_ADMIN_TERSE=true.
>>
>> If you want to know what it's doing while it's trying to start, use
>> --verbose.
>>
>> If you have some better ideas about how to handle this case, let me
>> know.
>>
>