Dynamic Reconfiguration

Dynamic reconfiguration allows you to make configuration changes to a runtime Web Server. You do not have to stop or restart the Web Server for the changes to take effect.

Dynamic configuration happens in one of the following ways:

• When you deploy a configuration through the Admin Console or CLI

• When you run the reconfig script in the server instance's bin directory

You can dynamically change the configuration settings in the obj.conf, mime.types, and ACL files without restarting the server. In addition, most settings in the server.xml file can be changed without restarting the server. If a server restart is required, a warning message appears in the server log when you deploy the configuration or run the reconfig command.

You cannot dynamically reconfigure the following server.xml configuration parameters:

• user

• temp-path

• log (with the exception of log-level)

• thread-pool

• pkcs11

• stats

• cgi

• dns

• dns-cache

• file-cache

• acl-cache

• ssl-session-cache

• access-log-buffer

• jvm (with exception of log-level)

If a misconfiguration occurs during dynamic reconfiguration, the server displays an error message. The server logs the error message to a log file specified by the previous known good configuration.

Certain misconfigurations result in warning messages but do not cause the server to reject the configuration. Other misconfigurations result in error messages and cause the server to reject the configuration. If the server rejects a configuration during startup, the server does not start. If the server rejects a configuration during dynamic reconfiguration, the server reverts to the previous known good configuration.