Configuration Changes Requiring Administrative Action

This page lists the set of configuration properties that require some form of administrative action for changes to take full effect.

Note that any changes to the java.properties file (which is used to specify the Java runtime and JVM options that should be used when running the Directory Server and associated tools) require that the dsjavaproperties tool be run to apply those changes. If the changes impact the Java runtime or JVM arguments used to run the Directory Server itself, then the server must be restarted.

Changelog Backend

• db-directory - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires that the Directory Server be stopped, the database directory manually relocated, and then the Directory Server restarted. While the Directory Server is stopped, the directory and files pertaining to this backend in the old database directory must be manually moved or copied to the new location.
• changelog-write-queue-capacity - The Changelog Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• je-property - Changes to this configuration property will only take effect if the Directory Server is restarted.

LDIF Backend

• ldif-file - The LDIF Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• is-private-backend - The LDIF Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

JE Backend

• db-directory - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires that the Directory Server be stopped, the database directory manually relocated, and then the Directory Server restarted. While the Directory Server is stopped, the directory and files pertaining to this backend in the old database directory must be manually moved or copied to the new location.
• is-private-backend - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• index-entry-limit - If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit. Setting a large limit (greater than 10,000) could have a big impact on write performance and database growth on disk.
• id2children-index-entry-limit - If this limit is increased, then the contents of the backend must be exported to LDIF and re-imported to allow the new limit to be used for any id2children keys that had already hit the previous limit.
• id2subtree-index-entry-limit - If this limit is increased, then the contents of the backend must be exported to LDIF and re-imported to allow the new limit to be used for any id2subtree keys that had already hit the previous limit.
• db-evictor-lru-only - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-evictor-nodes-per-scan - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-evictor-critical-percentage - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-log-file-max - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-logging-file-handler-on - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-logging-level - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-checkpointer-wakeup-interval - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-checkpointer-high-priority - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-num-lock-tables - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• db-clean-on-explicit-gc - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• default-cache-mode - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• id2entry-cache-mode - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• dn2id-cache-mode - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• id2children-cache-mode - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• id2subtree-cache-mode - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• dn2uri-cache-mode - The JE Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Local DB Backend

• large-attribute-type - If the set of large attribute types is altered to add an attribute which is already in use in this backend, or to remove an attribute which already has large values in an alternate backend, then it may be necessary to re-import or manually perform some kind of administrative operation to ensure that the backend contents are updated properly.

Large Attribute Backend

• is-private-backend - The Large Attribute Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• default-cache-mode - The Large Attribute Backend must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Logging Change Subscription Handler

• log-file - The Logging Change Subscription Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

JMX Connection Handler

• listen-port - The JMX Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• use-ssl - The JMX Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• ssl-cert-nickname - The JMX Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

LDAP Connection Handler

• listen-address - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• listen-port - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• use-ssl - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• ssl-cert-nickname - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• allow-tcp-reuse-address - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• max-cancel-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• num-request-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• request-handler-per-connection - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• ssl-client-auth-policy - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• accept-backlog - The LDAP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

HTTP Connection Handler

• listen-address - The HTTP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• listen-port - The HTTP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• use-ssl - The HTTP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• http-servlet-extension - The HTTP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• key-manager-provider - The HTTP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• trust-manager-provider - The HTTP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• num-request-handlers - The HTTP Connection Handler must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Crypto Manager

• ssl-cert-nickname - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

File System Entry Cache

• cache-type - The File System Entry Cache must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• cache-directory - The File System Entry Cache must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

FIFO Entry Cache

• min-cache-entry-value-count - The FIFO Entry Cache must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• min-cache-entry-attribute - The FIFO Entry Cache must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Global Configuration

• check-schema - Schema checking should only be disabled as a last resort since disabling schema checking harms performance and can lead to unexpected behavior in the server as well as the applications that access it. There are less severe options for addressing schema issues: 1. Update the data to conform to the server schema. 2. Modify the server schema to conform to the data. Contact support before modifying the server's default schema. 3. Change the single-structural-objectclass-behavior property to allow entries to have no structural object class or multiple structural object classes. 4. Change the invalid-attribute-syntax-behavior property to allow attribute values to violate their attribute syntax. 5. Change the allow-zero-length-values property of the Directory String Attribute Syntax configuration to allow attributes with this syntax to have a zero length value.
• large-attribute-backend - If the large attribute backend is changed, then the contents of that backend must be manually updated so that any large attribute information is in sync with the data for backends with large attributes.
• use-compact-sync-hist - The compact historical information encoding will not be backwards compatible with previous Directory Server versions and all historical data must be flushed before reverting back to a previous version by exporting the replicated base DN without the ds-sync-hist attribute and re-importing the data.
• encrypt-data - Note that enabling and/or disabling data encryption in a server that has existing data will not cause that data to be automatically encrypted or decrypted. That is, existing encrypted data will remain encrypted, and existing unencrypted data will remain unencrypted, until that data has been updated causing it to be rewritten. See the Directory Server documentation for information about how to safely apply the new encryption settings for all existing data.
• soft-delete-policy - Presently the server does not have an automatic purging capability for soft deleted entries. The directory administrator must periodically monitor and determine if too many soft deleted entries are consuming resources and must be pruned.

LDAP SDK Debug Logger

• queue-size - The LDAP SDK Debug Logger must be restarted if this property is changed and the asynchronous property is set to true.

Local DB Index

• index-entry-limit - If any index keys have already reached this limit, indexes must be rebuilt before they will be allowed to use the new limit. Setting a large limit (greater than 10,000) could have a big impact on write performance and database growth on disk.
• index-type - If any new index types are added for an attribute, and values for that attribute already exist in the database, the index must be rebuilt before it will be accurate.
• substring-length - The index must be rebuilt before it will reflect the new value.
• cache-mode - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Local DB VLV Index

• base-dn - The index must be rebuilt after modifying this property.
• scope - The index must be rebuilt after modifying this property.
• filter - The index must be rebuilt after modifying this property.
• sort-order - The index must be rebuilt after modifying this property.
• cache-mode - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

JDBC Based Access Log Publisher

• queue-size - The JDBC Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Operation Timing Access Log Publisher

• log-file - The Operation Timing Access Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Operation Timing Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Scripted File Based Access Log Publisher

• log-file - The Scripted File Based Access Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Scripted File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Audit Log Publisher

• queue-size - The File Based Audit Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Audit Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Writer Based Access Log Publisher

• queue-size - The Writer Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Admin Alert Access Log Publisher

• queue-size - The Admin Alert Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Access Log Publisher

• log-file - The File Based Access Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Third Party File Based Access Log Publisher

• log-file - The Third Party File Based Access Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Third Party File Based Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Debug Access Log Publisher

• log-file - The Debug Access Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Debug Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Error Log Publisher

• queue-size - The File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Error Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Third Party File Based Error Log Publisher

• log-file - The Third Party File Based Error Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Third Party File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Scripted File Based Error Log Publisher

• log-file - The Scripted File Based Error Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Scripted File Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Syslog Based Error Log Publisher

• queue-size - The Syslog Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

JDBC Based Error Log Publisher

• queue-size - The JDBC Based Error Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Detailed HTTP Operation Log Publisher

• log-file - The Detailed HTTP Operation Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Detailed HTTP Operation Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

Common Log File HTTP Operation Log Publisher

• log-file - The Common Log File HTTP Operation Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• queue-size - The Common Log File HTTP Operation Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.

File Based Debug Log Publisher

• queue-size - The File Based Debug Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Debug Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

File Based Sync Log Publisher

• queue-size - The File Based Sync Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The File Based Sync Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Sync Failed Ops Log Publisher

• queue-size - The Sync Failed Ops Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• log-file - The Sync Failed Ops Log Publisher must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Plugin

• plugin-type - The Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Seven Bit Clean Plugin

• plugin-type - The Seven Bit Clean Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Entry UUID Plugin

• plugin-type - The Entry UUID Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Periodic Stats Logger Plugin

• log-file - The Periodic Stats Logger Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Referral On Update Plugin

• plugin-type - The Referral On Update Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Delay Plugin

• plugin-type - The Delay Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Periodic GC Plugin

• plugin-type - The Periodic GC Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

DN Mapper Plugin

• plugin-type - The DN Mapper Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Attribute Mapper Plugin

• plugin-type - The Attribute Mapper Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

SNMP Subagent Plugin

• agentx-address - The SNMP Subagent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agentx-port - The SNMP Subagent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• num-worker-threads - The SNMP Subagent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Referential Integrity Plugin

• plugin-type - The Referential Integrity Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Change Subscription Notification Plugin

• plugin-type - The Change Subscription Notification Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Unique Attribute Plugin

• plugin-type - The Unique Attribute Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Changelog Password Encryption Plugin

• plugin-type - The Changelog Password Encryption Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Internal Search Rate Plugin

• plugin-type - The Internal Search Rate Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Processing Time Histogram Plugin

• plugin-type - The Processing Time Histogram Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• histogram-category-boundary - The Processing Time Histogram Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

SNMP Master Agent Plugin

• listen-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• listen-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agentx-listen-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agentx-listen-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• notification-target-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• notification-target-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agent-snmp-version - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• community-name - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agent-security-name - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• agent-security-level - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled
• num-worker-threads - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Pass Through Authentication Plugin

• plugin-type - The Pass Through Authentication Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Last Mod Plugin

• plugin-type - The Last Mod Plugin must be disabled and re-enabled (or the Directory Server restarted) for changes to this configuration property to take full effect. Modification requires that this component be disabled and then re-enabled

Replication Server

• replication-db-directory - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires that the Directory Server be stopped, the database directory manually relocated, and then the Directory Server restarted. While the Directory Server is stopped, the old database directory and its contents must be manually moved or copied to the new location.
• je-property - Changes to this configuration property will only take effect if the associated multimaster replication synchronization provider is disabled and re-enabled (or the Directory Server is restarted).

UnboundID Work Queue

• num-worker-threads - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-write-worker-threads - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-administrative-session-worker-threads - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-queues - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• num-write-queues - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• max-work-queue-capacity - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart
• queue-type - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

Wait Notify Work Queue

• num-worker-threads - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart

Traditional Work Queue

• max-work-queue-capacity - The Directory Server must be restarted for changes to this configuration property to take full effect. Modification requires a server restart