V B Kumar Jayanti wrote:
> I tried command asadmin stop-domain and saw the following strange ouput :
>
>> bash-3.2$ ./asadmin stop-domain
>> Waiting for the domain to stop
>> .................................................
>> ................................................................................
>>
>> ................................................................................
>>
>> ................................................................................
>>
>> ................................................................................
>>
>> ................................................................................
>>
>> ................................................................................
>>
>> ...............................................................
>> Timed out ({1} seconds) waiting for the domain to stop.
>> Command stop-domain failed.
>> bash-3.2$
>
>
> It actually waited for several seconds. This behaviour seems to occur
> if i first hit CTRL-C followed immediately by asadmin stop-domain in
> the same terminal.
>
> And when i tried asadmin stop-domain when the server is actually not
> running, i see
>
>> bash-3.2$ ./asadmin stop-domain
>> Waiting for the domain to stop ................
>> Command stop-domain executed successfully.
>> bash-3.2$
>
>
Ignore the second command output since i am unable to reproduce this
one. It actually gives me
> bash-3.2$ ./bin/asadmin.bat stop-domain
> Remote server does not listen for requests on [KUMAR:4,848].
> Is the server up?
> Command stop-domain failed.
rgds.
> With TP2 it used to give out a message like
>
>> bash-3.2$ ./asadmin.bat stop-domain
>> Cannot connect to host, is server up ?
>> Command stop-domain failed.
>> bash-3.2$
>
>
> Which IMO was better.
>
> rgds.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>