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 Data Store 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 Data Store itself, then the server must be restarted.

Attribute Syntax

• require-binary-transfer - The Data Store must be restarted for changes to this configuration property to take full effect. Changes to this property will take effect immediately for new attribute type definitions created after the change, but the change will not take effect for existing attributes with this syntax until the server is restarted.

Bit String Attribute Syntax

• enable-compaction - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact UnboundID for more information.

Integer Attribute Syntax

• enable-compaction - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact UnboundID for more information.

Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Alarm Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Alert Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Backup Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Changelog Backend

• db-directory - The Data Store must be restarted for changes to this configuration property to take full effect. Modification requires that the Data Store be stopped, the database directory manually relocated, and then the Data Store restarted. While the Data Store 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.
• db-cache-percent - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• changelog-write-queue-capacity - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• je-property - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

Config File Handler Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Encryption Settings Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

JE Backend

• db-directory - The Data Store must be restarted for changes to this configuration property to take full effect. Modification requires that the Data Store be stopped, the database directory manually relocated, and then the Data Store restarted. While the Data Store 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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• 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.
• exploded-index-entry-threshold - If any index keys have already reached this threshold, indexes need to be rebuilt before they are allowed to use the new threshold. 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-cache-percent - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-cleaner-min-utilization - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-evictor-critical-percentage - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-log-file-max - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-logging-level - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-num-cleaner-threads - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-txn-write-no-sync - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• je-property - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-recent-changes - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• default-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• id2entry-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• dn2id-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• id2children-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• id2subtree-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• dn2uri-cache-mode - The JE Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Large Attribute Backend

• enabled - DEPRECATION NOTE: The large attribute backend has been deprecated. It will continue to be supported for existing deployments already using the large attribute feature, but new deployments wishing for similar behavior should configure uncached attributes rather than large attributes.
• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration
• is-private-backend - The Large Attribute Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• db-cache-percent - The Large Attribute Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• default-cache-mode - The Large Attribute Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Local DB Backend

• uncached-id2entry-cache-mode - The Local DB Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

LDIF Backend

• ldif-file - The LDIF Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• is-private-backend - The LDIF Backend must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Monitor Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Schema Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Task Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Trust Store Backend

• base-dn - No administrative action is required by default although some action may be required on a per-backend basis before the new base DN may be used. Although it is currently supported, the use of multiple base DNs per backend is not recommended and this capability may be removed in the future. If you are considering the use of multiple base DNs in a backend, you should first contact UnboundID support to discuss this configuration

Logging Change Subscription Handler

• log-file - The Logging Change Subscription Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

HTTP Connection Handler

• listen-address - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• listen-port - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• use-ssl - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• http-servlet-extension - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• web-application-extension - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• key-manager-provider - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• trust-manager-provider - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-request-handlers - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• disable-tls-renegotiation - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• enable-multipart-mime-parameters - The HTTP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

JMX Connection Handler

• listen-port - The JMX Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• use-ssl - The JMX Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-cert-nickname - The JMX Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

LDAP Connection Handler

• listen-address - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• listen-port - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• use-ssl - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-cert-nickname - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• max-cancel-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-accept-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-request-handlers - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• ssl-client-auth-policy - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• accept-backlog - The LDAP Connection Handler must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Crypto Manager

• ssl-cert-nickname - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

FIFO Entry Cache

• min-cache-entry-value-count - The FIFO Entry Cache must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• min-cache-entry-attribute - The FIFO Entry Cache must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

File System Entry Cache

• cache-type - The File System Entry Cache must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• cache-directory - The File System Entry Cache must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Interactive Transactions Extended Operation Handler

• enabled - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact UnboundID for more information.

Validate TOTP Password Extended Operation Handler

• prevent-totp-reuse - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact UnboundID for more information.

Global Configuration

• location - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• invalid-attribute-syntax-behavior - DEPRECATION NOTE: The wholesale option to allow attribute values to violate their associated syntax has been deprecated. This is a very broad option and permits inadvertent corruption of the data over time. If you are trying to import legacy data with syntax violations, or if you have applications that may attempt to store values that violate the associated attribute syntax, then the recommended options to address this are as follows: * Update the legacy data so that all attribute values conform to the associated syntax, and update any applications that are known to try to store invalid values. * Modify the server schema to specify an alternate syntax for the attribute types for which there are known syntax violations. If there are indexes defined for any of the updated attribute types, then those indexes must be rebuilt. This option is only recommended for custom schema elements that are not shipped with the server. * Use the permit-syntax-violations-for-attribute property to specify the attribute types for which the server should allow non-compliant values. The permit-syntax-violations-for-attribute property should only be used if neither of the above options are possible, and you should be aware that the server may behave in unexpected ways when interacting with values that do not fit the constraints expected by the associated attribute syntax or matching rules.
• allow-inherited-replication-of-subordinate-backends - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact UnboundID for more information.
• 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 Data Store documentation for information about how to safely apply the new encryption settings for all existing data.
• database-on-virtualized-or-network-storage - See the Data Store documentation for information about how to safely apply this setting.
• encryption-settings-cipher-stream-provider - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact UnboundID for more information.
• allow-insecure-local-jmx-connections - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

HTTP Servlet Extension

• response-header - HTTP Connection Handlers hosting this HTTP Servlet Extension must be disabled and then re-enabled, or the server restarted, in order for this change to take effect.

Config HTTP Servlet Extension

• identity-mapper - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

File Server HTTP Servlet Extension

• base-context-path - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

SCIM HTTP Servlet Extension

• base-context-path - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• debug-enabled - The Data Store debug logger must be enabled and correctly configured for the debug messages to be forwarded.

LDAP Mapped SCIM HTTP Servlet Extension

• oauth-token-handler - The Data Store must be restarted for changes to this configuration property to take full effect. The OAuth Token Handler changes will not take effect until the associated HTTP Connection Handler is disabled and re-enabled, or until the server is restarted.
• basic-auth-enabled - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• include-ldap-objectclass - If you have specified a large number of object classes or used the '*' value you should ensure that the Data Store has been allocated a sufficient amount of memory (typically at least 512MB) to host the HTTP endpoints.

Metrics HTTP Servlet Extension

• identity-mapper - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

Policy Decision Point HTTP Servlet Extension

• identity-mapper - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

SCIM2 HTTP Servlet Extension

• base-context-path - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• debug-enabled - The Data Store debug logger must be enabled and correctly configured for the debug messages to be forwarded.

Velocity HTTP Servlet Extension

• identity-mapper - For this modification to take effect, you must either restart the server or disable then re-enable all HTTP Connection Handlers referencing this component.

JSON Field Constraints

• index-values - When adding a new JSON field index, you may need to use the rebuild-index tool to initialize the index based on existing data in the backend before the server will use or maintain that index. However, if the server can determine that either the backend is empty or the associated JSON field has never been used in any entries in the backend, then the new index may automatically be considered trusted. To determine whether an index needs to be initialized with the rebuild-index tool, use the command: dbtest list-database-containers --backendID {backendID} If the "Index Status" field has a value of "TRUSTED", then the server has determined that the JSON field is not used in the backend and it is not necessary to use rebuild-index to initialize that index. If the "Index Status" field has a different value (e.g., "UNTRUSTED" or "NEW"), then it needs to be initialized with the rebuild-index tool before it can be used.
• index-entry-limit - When increasing the index-entry-limit for a field that may contain values that have already exceeded the previous limit, you must use the rebuild-index tool (or export the contents of the backend to LDIF and re-import the data) before the new limit will be used for those values.

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.
• sign-log - The LDAP SDK Debug Logger must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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.
• substring-index-entry-limit - If this limit is increased, and any substring index keys have already reached the previous limit, then the substring index must be rebuilt to use the new limit.
• maintain-match-count-for-keys-exceeding-entry-limit - If the index is updated to maintain a match count after this capability has been disabled for any period of time, then the index must be rebuilt before the count can actually be maintained.
• exploded-index-entry-threshold - If any index keys have already reached this threshold, indexes need to be rebuilt before they are allowed to use the new threshold. 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 Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Access Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Debug Access Log Publisher

• log-file - The Debug Access Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Debug Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• sign-log - The Debug Access Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Audit Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Scripted File Based Access Log Publisher

• log-file - The Scripted File Based Access Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• 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.
• sign-log - The Scripted File Based Access Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Operation Timing Access Log Publisher must be restarted if this property is changed and the asynchronous property is set to true.
• sign-log - The Operation Timing Access Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• 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.
• sign-log - The Third Party File Based Access Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Common Log File HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• 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.

Detailed HTTP Operation Log Publisher

• log-file - The Detailed HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Detailed HTTP Operation Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• queue-size - The Detailed 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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Debug Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Error Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Scripted File Based Error Log Publisher

• log-file - The Scripted File Based Error Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• 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.
• sign-log - The Scripted File Based Error Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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.

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.

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• 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.
• sign-log - The Third Party File Based Error Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Sync Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

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 Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The Sync Failed Ops Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Writer Based Trace Log Publisher

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

File Based Trace Log Publisher

• log-file - The File Based Trace Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• sign-log - The File Based Trace Log Publisher must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Host System Monitor Provider

• enabled - Enabling host system cpu, memory, disk and network interface I/O monitoring requires running an external collector helper process except on Linux systems. Notes: - Enabling the host system monitor does not require restarting the server on Linux systems. - Enabling the host system monitor provider on UNIX (non-Linux) requires restarting the server. Changes to disk-devices and network-devices cannot be validated until the server is restarted. - Host system monitoring is not available on Windows systems.

Password Policy

• idle-lockout-interval - Last login time tracking is required for idle account lockout to work properly. If you are enabling idle account lockout, then you should ensure that the last-login-time-attribute and last-login-time-format properties are also defined and that last login time tracking has been enabled long enough so that user accounts have had time to be marked with last login times. Ideally, last login time tracking should be enabled for at least as long as the idle lockout interval to ensure that users are not incorrectly locked out merely because their accounts do not have last login time information.

Bcrypt Password Storage Scheme

• enabled - This password storage scheme implementation requires the Bouncy Castle JCE provider, which is not included with the Data Store, in order to simplify United States export control restrictions imposed on the distribution of cryptographic functionality. If you wish to use this feature, you must first obtain the necessary library from the Bouncy Castle website (https://bouncycastle.org/). This implementation has been compiled and tested with version 1.53 of the library, available in filehttps://www.unboundid.com/r/bouncycastle. This file should be placed in the "lib" directory beneath the server install root. The server will need to be restarted for this library to be available for use.

Scrypt Password Storage Scheme

• enabled - This password storage scheme implementation requires the Bouncy Castle JCE provider, which is not included with the Data Store, in order to simplify United States export control restrictions imposed on the distribution of cryptographic functionality. If you wish to use this feature, you must first obtain the necessary library from the Bouncy Castle website (https://bouncycastle.org/). This implementation has been compiled and tested with version 1.53 of the library, which can be obtained from the Bouncy Castle website using the linkhttps://www.unboundid.com/r/bouncycastle. This file should be placed in the "lib" directory beneath the server install root. The server will need to be restarted for this library to be available for use.

Plugin

• plugin-type - The Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Attribute Mapper Plugin

• plugin-type - The Attribute Mapper Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Change Subscription Notification Plugin

• plugin-type - The Change Subscription Notification Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Changelog Password Encryption Plugin

• plugin-type - The Changelog Password Encryption Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

DN Mapper Plugin

• plugin-type - The DN Mapper Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Delay Plugin

• plugin-type - The Delay Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Entry UUID Plugin

• plugin-type - The Entry UUID Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Internal Search Rate Plugin

• plugin-type - The Internal Search Rate Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

LDAP Result Code Tracker Plugin

• plugin-type - The LDAP Result Code Tracker Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Last Mod Plugin

• plugin-type - The Last Mod Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Monitor History Plugin

• log-file - The Monitor History Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Pass Through Authentication Plugin

• plugin-type - The Pass Through Authentication Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Periodic GC Plugin

• plugin-type - The Periodic GC Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Periodic Stats Logger Plugin

• log-file - The Periodic Stats Logger Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Stats Collector Plugin

• per-application-ldap-stats - When setting this option to per-application-only, you must also set the separate-monitor-entry-per-tracked-application property in the Processing Time Histogram Plugin to true.

Pre Update Config Plugin

• plugin-type - The Pre Update Config Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Processing Time Histogram Plugin

• plugin-type - The Processing Time Histogram Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• histogram-category-boundary - The Processing Time Histogram Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. The Metrics Engine can only aggregate response-time data when the boundary values are the same across both time and monitored servers. If you change the boundary values on one monitored server, you should change them on all monitored servers.
• separate-monitor-entry-per-tracked-application - When setting this option to true, you must also set the per-application-ldap-stats property in the Stats Collector Plugin to per-application-only.

Referential Integrity Plugin

• plugin-type - The Referential Integrity Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Referral On Update Plugin

• plugin-type - The Referral On Update Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

SNMP Master Agent Plugin

• listen-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• listen-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agentx-listen-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agentx-listen-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• notification-target-address - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• notification-target-port - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agent-snmp-version - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• community-name - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agent-security-name - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agent-security-level - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-worker-threads - The SNMP Master Agent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

SNMP Subagent Plugin

• agentx-address - The SNMP Subagent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• agentx-port - The SNMP Subagent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server
• num-worker-threads - The SNMP Subagent Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Seven Bit Clean Plugin

• plugin-type - The Seven Bit Clean Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Unique Attribute Plugin

• plugin-type - The Unique Attribute Plugin must be disabled and re-enabled (or the Data Store restarted) for changes to this configuration property to take full effect. In order for this modification to take effect, the component must be restarted, either by disabling and re-enabling it, or by restarting the server

Replication Server

• replication-db-directory - The Data Store must be restarted for changes to this configuration property to take full effect. Modification requires that the Data Store be stopped, the database directory manually relocated, and then the Data Store restarted. While the Data Store 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 Data Store is restarted).

UnboundID Ms Chap V2 SASL Mechanism Handler

• enabled - This SASL mechanism handler implementation requires the Bouncy Castle JCE provider, which is not included with the Data Store, in order to simplify United States export control restrictions imposed on the distribution of cryptographic functionality. If you wish to use this feature, you must first obtain the necessary library from the Bouncy Castle website (https://bouncycastle.org/). This implementation has been compiled and tested with version 1.53 of the library, available in filehttps://www.unboundid.com/r/bouncycastle. This file should be placed in the "lib" directory beneath the server install root. The server will need to be restarted for this library to be available for use.

UnboundID TOTP SASL Mechanism Handler

• prevent-totp-reuse - No further action is required for changes to this configuration property but there is other information that administrators should know about this property. Contact UnboundID for more information.

Replication Synchronization Provider

• num-update-replay-threads - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

Web Application Extension

• base-context-path - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• war-file - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• document-root-directory - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• deployment-descriptor-file - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• temporary-directory - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• init-parameter - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

Management Console Web Application Extension

• ldap-server - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• trust-store-file - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.
• log-file - For this modification to take effect, you must either restart the server or else disable and then re-enable any HTTP Connection Handler referencing this component.

Traditional Work Queue

• max-work-queue-capacity - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

UnboundID Work Queue

• num-worker-threads - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• num-write-worker-threads - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• num-administrative-session-worker-threads - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• num-queues - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• num-write-queues - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted
• max-work-queue-capacity - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted

Wait Notify Work Queue

• num-worker-threads - The Data Store must be restarted for changes to this configuration property to take full effect. In order for this modification to take effect the server must be restarted