yes Kedar did some change that were supposed to notify of server-restart
when the jvm-options are changed.
sof if this is not happening, we need to investigate.
jerome
Lloyd Chambers wrote:
> Anissa,
>
> Jerome made some changes in this area and so did Kedar. A
> ConfigListener was added for java-config. But I think it's not
> working right in that case. Any change to jvm-options should require a
> restart, so that listener is doing something wrong..
>
> Lloyd
>
> ..............................................
> Lloyd Chambers
> lloyd.chambers_at_sun.com
> GlassFish team, LSARC member
>
>
>
>
>
>
> On Oct 10, 2008, at 10:15 AM, Anissa Lam wrote:
>
>>
>> It used to be that creating a connection pool will show server
>> restart required. That seems to be fixed as i don't see that
>> anymore. Now, i need some case that will require server restart for
>> my testing. I have tried adding a <jvm-options>, change
>> <java-config> debug-enabled attribute, none of this shows server
>> restart is required. Is this true ?
>> Also, what CLI command will tell me that server require restart ?
>>
>> thanks
>> Anissa.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>