OPENDJ-3087 New baseDNs should be initialized with the most recent backend ...

Fabio Pistolesi

08.50.2016 4c5bb1673a6e5ce2fe38f6dc22b074787826b8fe

OPENDJ-3087 New baseDNs should be initialized with the most recent backend configuration

Creation of an additional suffix in a backend initialized the EntryContainer with the configuration read at start
instead of the one with all configuration changes applied, since any change in configuration was not recorded.
It may lead to data not being generated according to the settings and eventually to conflict with indexes in case of confidentiality.

 opendj-server-legacy/src/main/java/org/opends/server/backends/pluggable/RootContainer.java

@@ -68,7 +68,7 @@
  /** The ID of the backend to which this entry root container belongs. */
  private final String backendId;
  /** The backend configuration. */
  private final PluggableBackendCfg config;
  private volatile PluggableBackendCfg config;
  /** The monitor for this backend. */
  private BackendMonitor monitor;

@@ -450,8 +450,9 @@
  @Override
  public ConfigChangeResult applyConfigurationChange(PluggableBackendCfg configuration)
  {
    getMonitorProvider().enableFilterUseStats(configuration.isIndexFilterAnalyzerEnabled());
    getMonitorProvider().setMaxEntries(configuration.getIndexFilterAnalyzerMaxFilters());
    config = configuration;
    getMonitorProvider().enableFilterUseStats(config.isIndexFilterAnalyzerEnabled());
    getMonitorProvider().setMaxEntries(config.getIndexFilterAnalyzerMaxFilters());

    return new ConfigChangeResult();
  }