Hi Lidia,
Thanks for testing this information.
If this doc is inaccurate or out-of-date, would it be possible to file
an issue against the doc with details of the correct and up to date
information, so that the doc can be fixed?
For the text that is misleading, would the following rewrite be acceptable:
Managing the following services and resoures requires a restart:
* HTTP services
* IIOPservices
* JMS services
* JNDI resources
Regards,
-Paul
On 11/04/10 14:48, Lidia Marchioni wrote:
> Hello Paul
>
> Thank you very much, this is exactly what I was looking for. However,
> I have a couple of questions/comments, after going through some of the
> items mentioned in the document. Generally speaking many changes I
> tried did not trigger restart required message.
>
> I cannot trigger restart required modifying HTTP Service in v3.1. I
> tried enabling access logging and limiting access log files for a
> standalone instance but that does not trigger restart required message
> for that instance (neither in Admin GUI nor CLI). I tried enabling
> access logging for a standalone instance in v2.1.1, but that didn't
> trigger restart required either. Thus, what elements of HTTP Service
> need to be modified to trigger restart required?
>
> Documentation mentions that "Managing HTTP, JMS, IIOP, JNDI services"
> should trigger restart required. JNDI is under Resources, hence this
> message is misleading (HTTP, JMS, IIOP Services are under configuration).
>
> Impact of Configuration Changes document also mentions that the
> following will require server restart: "Creating or deleting resources
> (Exception: Some JDBC, JMS, or connector resources do not require
> restart.)". This is quite vague, but I created a JNDI Custom Resource
> in v3.1 and v2.1.1 to be sure, yet restart required message did not
> show up neither in Admin GUI nor CLI.
>
> Modifying "transaction-support" under "connector connection pool" is
> listed as requiring server restart. I created a connector connection
> pool with transaction support set to LocalTransaction. I then changed
> transaction support entry and saved it, yet restart was still not
> required... Tried it in v2.1.1 and behaviour was the same - no
> restart required when modifying transaction support. Looks like
> documentation needs to be updated here? Could someone confirm
> please? I have not tested all the elements mentioned in the document
> yet...
>
> Thanks
> Lidia
>
>
> Paul M Davies (Oracle) wrote:
>> Hi,
>>
>> The section Impact of Configuration Changes
>> <http://docs.sun.com/doc/821-1751/gitzw> in the 3.0.1 Admin Guide
>> describes changes that require a restart and dynamic changes.
>>
>> Regards,
>> -Paul
>>
>> On 11/02/10 11:10, Lidia Marchioni wrote:
>>> Hi
>>>
>>> I need to test "Restart Required with reason" in Admin Console and
>>> was wondering if there is a way to determine when restart of a
>>> server instance should be required. Is there any document that
>>> would help find out all such conditions?
>>>
>>> Thanks
>>> Lidia
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>>
>>
>>
>> --
>>
>>
>>
>> Oracle <http://www.oracle.com>
>> Paul Davies| Principal Technical Writer| +1.408.276.3413
>> Oracle GlassFish Server Documentation
>> 4140 Network Circle, Santa Clara CA 95054, USA
>>
>> Green Oracle <http://www.oracle.com/commitment> Oracle is committed
>> to developing practices and products that help protect the environment
>>
>>
--
Oracle <http://www.oracle.com>
Paul Davies| Principal Technical Writer| +1.408.276.3413
Oracle GlassFish Server Documentation
4140 Network Circle, Santa Clara CA 95054, USA
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment