Right. Almost all changes should be detected and things restarted
accordingly behind the scenes for you. There might be some holes
surrouding http-service and virtual-servers but everything under
network-config and thread-pools should be caught properly.
On 8/12/10 9:05 AM, Oleksiy Stashok wrote:
> Hi Tim,
>
> it should work without restart.
> Let us know if it doesn't.
>
> WBR,
> Alexey.
>
> On Aug 12, 2010, at 14:47 , Tim Quinn wrote:
>
>> Hi. Apologies if this is documented somewhere and I've missed it.
>>
>> As part of implementing secure admin in GlassFish, a user can run a
>> command which (among other things) will change some of the Grizzly
>> config for the admin listener (turn on/off port unification, turn
>> on/off redirection of http -> https, set/clear using SSL/TLS,
>> set/clear the certificate alias to use in SSL/TLS authentication,
>> turn on/off client-auth=want).
>>
>> If we changes these config settings, does Grizzly need the server to
>> restart for those changes to take effect?
>>
>> Thanks.
>>
>> - Tim
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>