quality@glassfish.java.net

Re: Waiting for DAS to start. ...................................................

From: Kedar Mhaswade <Kedar.Mhaswade_at_Sun.COM>
Date: Fri, 02 Oct 2009 11:53:22 -0700

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.

I agree, this is difficult to get right.

Making verbose a default is incompatible with other releases and
would certainly break scripts. But making the server start in verbose
by default would make *developers* happy because they would mostly
know what's going on (again, that depends upon what logging activity
happens during this period).

The point of the complaint that I thought was something we could be
better at was
- At times, sitting quietly doing nothing is analogous to
   printing more and more dots. It just makes the user wait without
   knowing what's going on.

>
>
> kedar wrote on 10/02/09 09:43:
>> Cay,
>>
>> I acknowledge that this can be annoying. And yes, DAS really does not
>> mean anything you'd know as far as v3 is concerned. So, I gather that
>> you'd
>> like asadmin tool to do the following:
>> - If the server does not start after a certain number of "dots" (say
>> 5), then
>> see what could be wrong instead of just printing more dots.
>> - Change "Waiting for DAS to start" to something more meaningful. Would
>> "Waiting for server to start" make more sense?
>>
>> Let us know and we'll work on a fix.
>>
>> Also, would you please provide your platform details, whether it happens
>> standalone or via Eclipse/NetBeans etc?
>>
>> Regards,
>> Kedar
>>
>> PS - users who know v2 may know of DAS, but as of now, v3 has no
>> concept of
>> a Domain Admin Server.
>>
>> Cay Horstmann wrote:
>>> Thanks, I'll try that. I just had another issue with DAS not starting
>>> inside Eclipse. It worked on the second try.
>>>
>>> Sherry Shen wrote:
>>>> Hi Cay,
>>>>
>>>> Thanks for using glassfish and providing feedback.
>>>> % asadmin start-domain --verbose
>>>> Oct 2, 2009 7:35:17 AM
>>>> com.sun.enterprise.admin.launcher.GFLauncherLogger info
>>>> INFO: JVM invocation command line:
>>>> /space/test1/tool/jdk1.6.0_14/bin/java
>>>> .....
>>>>
>>>> If you can reproduce your issue again, please try to use --verbose to
>>>> diagnose the reason.
>>>>
>>>> Best Regards,
>>>>
>>>> Sherry
>>>> Cay Horstmann wrote, On 10/2/2009 8:03 AM:
>>>>
>>>>> I know that. At least the older versions didn't show that
>>>>> irritating sequence of dots. My point is that instead of adding
>>>>> that embellishment we could perhaps expend some effort diagnosing
>>>>> the reason when the DAS fails to start.
>>>>>
>>>>> Wouter van Reeven wrote:
>>>>>
>>>>>> Hi Cay,
>>>>>>
>>>>>>
>>>>>> Older builds of GlassFish also display the message "Waiting for
>>>>>> DAS to
>>>>>> start" but it continues very quickly after displaying that message.
>>>>>> Looks like either your domain is misconfigured or you ran into a bug.
>>>>>>
>>>>>>
>>>>>> HTH, Wouter
>>>>>>
>>>>>> On Fri, Oct 02, 2009 at 04:34:38PM +0200, jerome moliere wrote:
>>>>>>
>>>>>>> Hi Cay,
>>>>>>> it seems that your problem is related to the clustering main
>>>>>>> component....
>>>>>>> DAS stands for Domain Agents Server in the Glassfish vocabulary
>>>>>>>
>>>>>>>
>>>>>>> HTH
>>>>>>> Jerome
>>>>>>> 2009/10/2 Cay Horstmann <cay_at_horstmann.com>
>>>>>>>
>>>>>>> I just upgraded to b66.
>>>>>>>
>>>>>>> Here is what I got.
>>>>>>>
>>>>>>> $ asadmin start-domain --domaindir /home/domains
>>>>>>> Waiting for DAS to start.
>>>>>>>
>>>>>>> ......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
.
>>>>>>>
>
>>
>>
>>>>>>>
>>>>>>
>>>>> .......
>>>>>
>>>>>>>
>>>>>>> ...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
>>>>>>>
>>>>>>>
>>>>>>> That long line of dots did not brighten my morning.
>>>>>>>
>>>>>>> I don't know what DAS is or why I need to wait for it to
>>>>>>> start. And then
>>>>>>> when it didn't start, why add insult to injury by printing
>>>>>>> out these dots?
>>>>>>> How about instead printing out a message that tells me what I
>>>>>>> can do when
>>>>>>> it doesn't start?
>>>>>>>
>>>>>>> I ended up killing the process and trying again. It worked
>>>>>>> the next time.
>>>>>>>
>>>>>>> Cay
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Cay S. Horstmann | http://horstmann.com |
>>>>>>> mailto:cay_at_horstmann.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail:
>>>>>>> quality-unsubscribe_at_glassfish.dev.java.net
>>>>>>> For additional commands, e-mail:
>>>>>>> quality-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jerome Moliere - Mentor/J
>>>>>>> http://romjethoughts.blogspot.com/
>>>>>>> auteur Eyrolles
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>>>>
>>>>
>>>
>>>
>