admin@glassfish.java.net

Re: New Feature: Remote Restart

From: Lloyd Chambers <Lloyd.Chambers_at_Sun.COM>
Date: Thu, 09 Apr 2009 10:02:37 -0700

Byron,

I don't understand— if it's a remote server how can there be "no
security issues": isn't there at least a username/password for the
watchdog process?

Lloyd

On Apr 7, 2009, at 5:25 PM, Byron Nevins wrote:

>
>
> Lloyd Chambers wrote:
>>
>> Byron,
>>
>> Very nice!
>>
> Thanks!
>> What are the security aspects here?
> Whatever command line you used to start the server is used to
> restart it. The owner of the watchdog process remains the same so
> there are no security issues.
>>
>> Can it be done programmatically eg can the server restart itself?
> Sure -- you can run the RestartDomainCommand in the server. It of
> course needs the help of the watchdog to restart.
>
>>
>> Lloyd
>>
>> On Apr 7, 2009, at 11:46 AM, Byron Nevins wrote:
>>
>>> A new feature is now in place: Remote Server Restart
>>>
>>> How to use it:
>>>
>>> 1) start a domain with asadmin. You don't need to specify any
>>> special options. It will automatically start both the domain and
>>> a "watchdog" process. The watchdog is very lightweight. It will
>>> not block and it will return once it has verified that the domain
>>> has started. So scripts that start domains should work exactly as
>>> before.
>>> e.g. asadmin start-domain
>>>
>>> 2) to restart the domain, run this remote command from any computer:
>>> asadmin restart-domain
>>>
>>> 3) to stop the domain and the watchdog simply run
>>> asadmin stop-domain
>>>
>>> Notes:
>>> To NOT start the watchdog you need to run start-domain with the "--
>>> nowatchdog" option.
>>> You can start the domain with the --verbose option and it will be
>>> a watchdog and will echo all server log messages
>>> The watchdog process owns no window and its name in jps will
>>> appear as ASWatchdog
>>> In Verbose mode the name will appear as before and it does have a
>>> window and it blocks on the domain.
>>> If you try the restart-domain on a domain that was started with no
>>> watchdog - it is (by definition) an error and the domain will not
>>> be stopped.
>>> Killing the server always kills the watchdog automatically. Vice
>>> versa will be true too when the issue below is fixed.
>>> Known Issue:
>>> If you kill the watchdog process it will not kill the server. It
>>> will eventually do this exactly like verbose handles ^C entered at
>>> the console
>>>
>>> --
>>> Byron Nevins Work 408-276-4089, Home 650-359-1290, Cell
>>> 650-784-4123 - Sun Microsystems, Inc.
>>> --------------------------------------------------------------------- To
>>> unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net For
>>> additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>> Lloyd Chambers
>> lloyd.chambers_at_sun.com
>> GlassFish Team
>>
>>
>>
>
> --
> Byron Nevins Work 408-276-4089, Home 650-359-1290, Cell 650-784-4123
> - Sun Microsystems, Inc.
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net For
> additional commands, e-mail: admin-help_at_glassfish.dev.java.net

Lloyd Chambers
lloyd.chambers_at_sun.com
GlassFish Team