After Disabling Dynamic Reconfiguration Oracle GlassFish Server Still Performs Dynamic Configuration Changes

(Doc ID 1402213.1)

Last updated on FEBRUARY 24, 2017

Applies to:

Oracle GlassFish Server - Version: 3.1.1 and later   [Release: 3.1 and later ]
Information in this document applies to any platform.

Symptoms

Dynamic reconfiguration flag is not honored by Oracle GlassFish Server 3.1.1.

Steps to reproduce:

1) Disable dynamic reconfiguration:

$ asadmin set server-config.dynamic-reconfiguration-enabled=false


2) Restart the GlassFish Server for this change to take effect

3) Change some attribute, e.g. an HTTP listener's port:

$ asadmin set server-config.network-config.network-listeners.network-listener.http-listener-1.port=5555
server-config.network-config.network-listeners.network-listener.http-listener-1.port=5555
Command set executed successfully.

4) Since dynamic reconfiguration is disabled, changes shouldn't be applied until the server is restarted. However, Glassfish binds to the new port right away:


[#2011-12-1310:53:02.111+0000|INFO|oracle-glassfish3.1.1|javax.enterprise.syst
em.container.web.com.sun.enterprise.web|_ThreadID=26;_ThreadName=Thread-2;|WEB
0169: Created HTTP listener [http-listener-1] on host/port [0.0.0.0:5555]#]

[#2011-12-1310:53:02.552+0000|INFO|oracle-glassfish3.1.1|javax.enterprise.syst
em.container.web.com.sun.enterprise.web|_ThreadID=27;_ThreadName=Thread-2;|WEB
0169: Created HTTP listener [http-listener-1] on host/port [0.0.0.0:5555]#]

[#2011-12-1310:53:02.584+0000|INFO|oracle-glassfish3.1.1|javax.enterprise.syst
em.core.com.sun.enterprise.v3.services.impl|_ThreadID=28;_ThreadName=Thread-2;
|Grizzly Framework 1.9.40 started in: 6ms - bound to [0.0.0.0:5555]#]

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms