Uses of Class
org.forgerock.i18n.LocalizableMessageDescriptor.Arg3
Packages that use LocalizableMessageDescriptor.Arg3
Package
Description
This package provides an alternative localization mechanism to
org.slf4j.cal10n.APIs for implementing lightweight REST to LDAP gateways.
This package contains LDAP schema syntaxes and matching rules for JSON based attributes.
Defines all the messages that may be used in the Directory Server and tools.
Contains various implementations of Directory Server APIs that are not appropriate for other packages.
Contains implementations for a number of Directory Server data types.
-
Uses of LocalizableMessageDescriptor.Arg3 in org.forgerock.i18n.slf4j
Methods in org.forgerock.i18n.slf4j with parameters of type LocalizableMessageDescriptor.Arg3Modifier and TypeMethodDescription<T1,T2, T3>
voidLocalizedLogger.error(LocalizableMessageDescriptor.Arg3<T1, T2, T3> d, T1 a1, T2 a2, T3 a3) Logs an error message.<T1,T2, T3>
voidLocalizedLogger.info(LocalizableMessageDescriptor.Arg3<T1, T2, T3> d, T1 a1, T2 a2, T3 a3) Logs a message at INFO level.<T1,T2, T3>
voidLocalizedLogger.note(LocalizableMessageDescriptor.Arg3<T1, T2, T3> d, T1 a1, T2 a2, T3 a3) Logs a message at NOTICE level.<T1,T2, T3>
voidLocalizedLogger.warn(LocalizableMessageDescriptor.Arg3<T1, T2, T3> d, T1 a1, T2 a2, T3 a3) Logs a warning message. -
Uses of LocalizableMessageDescriptor.Arg3 in org.forgerock.opendj.hdap
Fields in org.forgerock.opendj.hdap declared as LocalizableMessageDescriptor.Arg3Modifier and TypeFieldDescriptionHdapMessages.ERR_ERROR_RESPONSEAn error occurred while processing the request '%s': '%s' (details: '%s') -
Uses of LocalizableMessageDescriptor.Arg3 in org.forgerock.opendj.json.schema
Fields in org.forgerock.opendj.json.schema declared as LocalizableMessageDescriptor.Arg3Modifier and TypeFieldDescriptionSchemaMessages.ERR_JSON_PARSE_ERRORThe value could not be parsed as valid JSON because a syntax error was detected on line %d column %d: %s -
Uses of LocalizableMessageDescriptor.Arg3 in org.opends.messages
Fields in org.opends.messages declared as LocalizableMessageDescriptor.Arg3Modifier and TypeFieldDescriptionServerMessages.DSBACKUP_BACKUP_PROGRESS_STATUSBacking up file (%d/%d) '%s'ServerMessages.DSBACKUP_ERROR_DURING_RESTOREAn error occurred while attempting to restore backend '%s' with backup ID '%s': %sServerMessages.DSBACKUP_PURGE_PROGRESS_STATUSPurging backup (%d/%d) '%s'ServerMessages.DSBACKUP_RESTORE_PROGRESS_STATUSRestoring file (%d/%d) '%s'ServerMessages.DSBACKUP_VERIFY_PROGRESS_STATUSVerifying file (%d/%d) '%s'ServerMessages.ERR_ATTR_SYNTAX_DN_ATTR_ILLEGAL_CHARThe provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not allowed in an attribute nameServerMessages.ERR_ATTR_SYNTAX_DN_INVALID_CHARThe provided value "%s" could not be parsed as a valid distinguished name because character '%c' at position %d is not validServerMessages.ERR_ATTR_SYNTAX_DN_NO_EQUALThe provided value "%s" could not be parsed as a valid distinguished name because the next non-space character after attribute name "%s" should have been an equal sign but instead was '%c'ServerMessages.ERR_BACKEND_FAULTY_CRYPTO_TRANSFORMATIONError while enabling confidentiality with cipher %s, %d bits: %sServerMessages.ERR_BACKEND_TOOL_NO_TREE_FOR_NAMENo index exists with the requested name '%s' in base DN '%s' and backend '%s'ServerMessages.ERR_CACHE_INVALID_EXCLUDE_FILTERThe ds-cfg-exclude-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are excluded from the cache, has an invalid value of "%s": %sServerMessages.ERR_CACHE_INVALID_INCLUDE_FILTERThe ds-cfg-include-filter attribute of configuration entry %s, which specifies a set of search filters that may be used to control which entries are included in the cache, has an invalid value of "%s": %sServerMessages.ERR_CANNOT_INSTANTIATE_BACKEND_CLASSUnable to create an instance of class %s referenced in configuration entry %s as a Directory Server backend: %sServerMessages.ERR_CANNOT_LIST_SECRET_FILES'%s' cannot list the secret files in directory '%s', all the secrets will be ignored: %sServerMessages.ERR_CANNOT_LOAD_BACKEND_CLASSUnable to load class %s referenced in configuration entry %s for use as a Directory Server backend: %sServerMessages.ERR_CANNOT_RENAME_CONFLICT_ENTRYAn error happened trying to rename a conflicting entry. DN: %s, Operation: %s, Result: %sServerMessages.ERR_CHANGELOG_BACKEND_ATTRIBUTEAn error occurred when retrieving attribute value for attribute '%s' for entry DN '%s' in changelog backend : %sServerMessages.ERR_CHANGELOG_BACKEND_EXCEPTION_ENCODING_ENTRYAn exception was encountered while trying to encode a replication %s message for entry "%s" into an External Change Log entry: %sServerMessages.ERR_CHANGELOG_BACKEND_SEARCHAn error occurred when searching base DN '%s' with filter '%s' in changelog backend : %sServerMessages.ERR_CHANGELOG_CANNOT_READ_NEWEST_RECORDCould not position and read newest record from log file '%s'. Current thread is '%s'. Error was: %sServerMessages.ERR_CHANGELOG_READER_UNABLE_TO_POSITIONUnable to position reader to key '%s' using strategy '%s' on log '%s'. Changelog may be corrupted. Directory servers connected to this replication server may need to be reinitializedServerMessages.ERR_CHANGELOG_UNABLE_TO_ADD_RECORDCould not add record '%s' in log file '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_CREATE_CN_INDEX_DBCould not get or create change number index DB in root path '%s', using path '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_CREATE_SERVER_ID_DIRECTORYCould not create directory '%s' for server id %s: %sServerMessages.ERR_CHANGELOG_UNABLE_TO_DELETE_GENERATION_ID_FILECould not delete generation id file '%s' for DN '%s': %sServerMessages.ERR_CHANGELOG_UNABLE_TO_UPDATE_DOMAIN_STATE_FILECould not create a new domain id %s for domain DN %s and save it in the domain state file. Replication will continue, but if the domain state file cannot be written when stopping the server, it should be restored from backup. Cause was : %sServerMessages.ERR_CHANGELOG_UNKNOWN_LOG_FILE_VERSIONChangelog file %s should be version %d, but found version %d. Likely causes for this error: the server binaries were accidentally downgraded, data was restored from a file system backup taken on a more recent version of the server, or the changelog file was corrupted. If the server was downgraded, upgrade it. If the data was restored from a file system backup, restore it again from a recent, valid file system backup taken on the same version of the server. Otherwise, as last resort, remove the changelog by running the 'dsrepl clear-changelog' command and restart the serverServerMessages.ERR_COMMON_AUDIT_EXTERNAL_HANDLER_JSON_FILEError while reading JSON configuration file %s while creating common audit external log publisher %s: %sServerMessages.ERR_COMMON_AUDIT_INVALID_TIME_OF_DAYError while processing common audit log publisher %s, time of the day value '%s' for fixed time log rotation policy is not valid, it should use a 24-hour format "HHmm" : %sServerMessages.ERR_CONFIG_ACCTNOTHANDLER_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as an account status notification handler as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_ALERTHANDLER_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as an alert handler as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_ATTR_INT_ABOVE_UPPER_BOUNDUnable to set the value for configuration attribute %s because the provided value %d is greater than the largest allowed value of %dServerMessages.ERR_CONFIG_ATTR_INT_BELOW_LOWER_BOUNDUnable to set the value for configuration attribute %s because the provided value %d is less than the lowest allowed value of %dServerMessages.ERR_CONFIG_ATTR_INVALID_INT_VALUEUnable to set the value for integer configuration attribute %s because the provided value %s cannot be interpreted as an integer value: %sServerMessages.ERR_CONFIG_AUTHZ_UNABLE_TO_INSTANTIATE_HANDLERAn error occurred while attempting to instantiate class %s referenced in the access control configuration entry %s: %sServerMessages.ERR_CONFIG_BACKEND_CANNOT_INITIALIZEAn error occurred while trying to initialize a backend loaded from class %s with the information in configuration entry %s: %s. This backend will be disabledServerMessages.ERR_CONFIG_BACKEND_CANNOT_INSTANTIATEThe Directory Server was unable to load class %s and use it to create a backend instance as defined in configuration entry %s. The error that occurred was: %s. This backend will be disabledServerMessages.ERR_CONFIG_CERTMAPPER_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as a certificate mapper as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_CHANGE_NO_RESULT%s.%s returned a result of null for entry %sServerMessages.ERR_CONFIG_CONNHANDLER_CANNOT_INITIALIZEAn error occurred while trying to initialize a connection handler loaded from class %s with the information in configuration entry %s: %s. This connection handler will be disabledServerMessages.ERR_CONFIG_EXTOP_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as an extended operation handler as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_EXTOP_INVALID_CLASSClass %s specified in configuration entry %s does not contain a valid extended operation handler implementation: %sServerMessages.ERR_CONFIG_FILE_ADD_FAILEDAn unexpected error occurred while attempting to add configuration entry %s as a child of entry %s: %sServerMessages.ERR_CONFIG_FILE_ADD_REJECTED_BY_LISTENERThe Directory Server is unwilling to add configuration entry %s because one of the add listeners registered with the parent entry %s rejected this change with the message: %sServerMessages.ERR_CONFIG_FILE_DELETE_FAILEDAn unexpected error occurred while attempting to remove configuration entry %s as a child of entry %s: %sServerMessages.ERR_CONFIG_FILE_DELETE_REJECTED_BY_LISTENEREntry %s cannot be removed from the Directory Server configuration because one of the delete listeners registered with the parent entry %s rejected this change with the message: %sServerMessages.ERR_CONFIG_FILE_INVALID_BASE_DNThe first entry read from LDIF configuration file %s had a DN of "%s" rather than the expected "%s" which should be used as the Directory Server configuration rootServerMessages.ERR_CONFIG_FILE_MODIFY_FAILEDAn unexpected error occurred while attempting to modify configuration entry %s as a child of entry %s: %sServerMessages.ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_NEW_CONFIGAn error occurred while attempting to rename the new Directory Server configuration from file %s to %s: %sServerMessages.ERR_CONFIG_HTTPENDPOINT_CONFLICTING_AUTHZ_DNThe HTTP endpoint configuration defined in %s is referencing mutually exclusive authorization DNs %s and %sServerMessages.ERR_CONFIG_HTTPENDPOINT_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as an HTTP endpoint as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_IDMAPPER_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as an identity mapper as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_INVALID_BIG_INDEX_INCLUDED_VALUEIndex for attribute '%s' cannot be created because the configuration contains an included attribute value '%s' which appears to be invalid according to the schema: %sServerMessages.ERR_CONFIG_KEYMANAGER_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as a key manager provider as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_LOGGER_INVALID_ACCESS_LOGGER_CLASSClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server access logger: %sServerMessages.ERR_CONFIG_LOGGER_INVALID_ERROR_LOGGER_CLASSClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server error logger: %sServerMessages.ERR_CONFIG_LOGGER_INVALID_HTTP_ACCESS_LOGGER_CLASSClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server HTTP access logger: %sServerMessages.ERR_CONFIG_LOGGING_CANNOT_OPEN_FILEAn error occurred while attempting to open the configured log file %s for logger %s: %sServerMessages.ERR_CONFIG_OAUTH2_INVALID_JSON_POINTERThe OAuth2 authorization mechanism defined in %s contains an invalid JSON Pointer %s: %sServerMessages.ERR_CONFIG_OAUTH2_INVALID_URLThe authorization mechanism defined in %s is referencing an invalid URL %s: %sServerMessages.ERR_CONFIG_PLUGIN_CANNOT_INITIALIZEAn error occurred while attempting to initialize an instance of class %s as a Directory Server plugin using the information in configuration entry %s: %s. This plugin will be disabledServerMessages.ERR_CONFIG_PWGENERATOR_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as a password generator as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_PWSCHEME_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as a password storage scheme as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_PWVALIDATOR_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as a password validator as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_RETENTION_POLICY_INVALID_CLASSClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log retention policy: %sServerMessages.ERR_CONFIG_ROTATION_POLICY_INVALID_CLASSClass %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log rotation policy: %sServerMessages.ERR_CONFIG_SASL_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as a SASL mechanism handler as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_SCHEMA_PROVIDER_CANT_BE_INITIALIZEDThe schema provider class '%s' could not be instantiated or initialized with the configuration '%s' : %sServerMessages.ERR_CONFIG_SYNCH_UNABLE_TO_INSTANTIATE_PROVIDERAn error occurred while attempting to instantiate class %s referenced in synchronization provider configuration entry %s: %sServerMessages.ERR_CONFIG_TRUSTMANAGER_INITIALIZATION_FAILEDAn error occurred while trying to initialize an instance of class %s as a trust manager provider as defined in configuration entry %s: %sServerMessages.ERR_CONFIG_VATTR_INITIALIZATION_FAILEDAn error occurred while trying to load an instance of class %s referenced in configuration entry %s as a virtual attribute provider: %sServerMessages.ERR_CONFIG_VATTR_INVALID_SEARCH_FILTERUnable to parse value "%s" from config entry "%s" as a valid search filter: %sServerMessages.ERR_CONFIG_VATTR_SV_TYPE_WITH_MV_PROVIDERThe virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but provider %s may generate multiple valuesServerMessages.ERR_CONFIG_VLV_INDEX_BAD_FILTERAn error occurred while parsing the search filter %s defined for VLV index %s: %sServerMessages.ERR_CONFIG_WORK_QUEUE_INITIALIZATION_FAILEDUnable to initialize an instance of class %s as a work queue as specified in configuration entry %s: %sServerMessages.ERR_CONNECTION_CLOSED%s connection %s has been closed because the connection handler %s is shutting downServerMessages.ERR_COULD_NOT_ADD_CHANGE_TO_SHUTTING_DOWN_REPLICA_DBCould not add change %s to replicaDB %s %s because flushing thread is shutting downServerMessages.ERR_CRYPTOMGR_DECODE_SYMMETRIC_KEY_ATTRIBUTE_SYNTAXCryptoManager symmetric key attribute value "%s" syntax is invalid. Parsing failed in field "%s" at offset %dServerMessages.ERR_DISK_SPACE_FULL_THRESHOLD_REACHEDThe free space (%s) on the disk containing directory "%s" is below full threshold for the following subsystems: %s. Write operations to the backend, replication updates included, will fail until the free space rises above the thresholdServerMessages.ERR_DISK_SPACE_LOW_THRESHOLD_REACHEDThe free space (%s) on the disk containing directory "%s" is between low and full threshold for the following subsystems: %s. Write operations are only permitted by a user with the BYPASS_LOCKDOWN privilege until the free space rises above the threshold. Replication updates are still allowedServerMessages.ERR_DISK_SPACE_THRESHOLDS_PER_SUBSYSTEM"%s" (low=%s, full=%s)ServerMessages.ERR_DS_DURING_HANDSHAKEDirectory server %s was attempting to connect to replication server %s but an error occurred in handshake phase. Error: %sServerMessages.ERR_DS_INVALID_REQUESTED_STATUSReceived invalid requested status %s in DS replication domain %s with server id %sServerMessages.ERR_DS_STATE_IS_TOO_LATEChangelog on replication server '%s' no longer contains changes for domain '%s' which are required by replica '%s'. The replica will no longer receive replicated changes and must be re-initializedServerMessages.ERR_DSREPL_DR_CANNOT_CLEAR_CHANGELOGAn error occurred while clearing the changelog for the domain '%s'. This server will not be able to connect to the servers which have already completed the disaster recovery procedure. Make sure the filesystem at '%s' is readable with delete permissions and try again. The error is: %sServerMessages.ERR_DSREPL_DR_CANNOT_REWRITE_REPLICATION_DATAAn error occurred while rewriting replication data for the domain '%s'. This server will not be able to connect to the servers which already have received the disaster recovery procedure. Make sure the filesystem at '%s' is writeable and there is some free disk space and try again. The error is: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_ADD_ENTRYCannot add the entry '%s' to the server '%s'. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_BOOTSTRAP_REPL_SERVERSCannot add '%s' to the bootstrap replication server list on server '%s'. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_REPL_SERVERCannot add '%s' to the configuration of replication server on server '%s'. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_DETERMINE_SERVER_IDCannot determine server ID for server '%s' on DNs '%s' and '%s'ServerMessages.ERR_DSREPL_MIGRATION_CANNOT_MODIFY_ENTRYCannot modify the entry '%s' on server '%s' to reconcile it with what is expected by the tool. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_READ_ENTRYCannot read the entry '%s' on server '%s'. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_SERVER_ID_ALREADY_USEDCannot use server ID '%s' for the local server because it is already used by server '%s' (configuration object %s)ServerMessages.ERR_DYNAMICGROUP_CANNOT_DECODE_MEMBERURLUnable to decode value "%s" in entry "%s" as an LDAP URL: %sServerMessages.ERR_EMBEDDED_SERVER_IMPORT_DATA_FAILUREAn error occurred while attempting to import LDIF file '%s' into embedded server with instance path '%s': '%s'ServerMessages.ERR_EMBEDDED_SERVER_IMPORT_DATA_NOT_SUCCESSFULAn error occurred while attempting to import LDIF file '%s' into embedded server with instance path '%s'. Import LDIF task state was '%s'. You can look at the task logs printed on the embedded server output stream for more detailsServerMessages.ERR_EMBEDDED_SERVER_SETUP_EXTRACT_ARCHIVEAn error occurred while attempting to extract server archive '%s' before setup of embedded server with install path '%s': %sServerMessages.ERR_ENCPW_NO_CLEAR_PWNo clear-text password was specified. Use --%s, --%s or --%s to specify the password to encodeServerMessages.ERR_ERROR_STARTING_CONNECTION_HANDLERCould not start connection handler %s with listen addresses "%s". The error was: %sServerMessages.ERR_EXACTMAP_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'ServerMessages.ERR_EXCEPTION_CHANGING_STATUS_AFTER_RESET_GEN_IDCaught IOException while changing status for domain %s and serverId: %s after reset for generation id: %sServerMessages.ERR_EXCEPTION_SENDING_CSReplication broker with dn %s and server id %s failed to signal status change because of: %sServerMessages.ERR_FCM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINThe certificate with fingerprint '%s' could not be mapped to exactly one user. It maps at least to both '%s' and '%s'ServerMessages.ERR_FILE_KEYMANAGER_INVALID_TYPEThe keystore type %s specified in attribute ds-cfg-key-store-type of configuration entry %s is not valid: %sServerMessages.ERR_FILE_REPLICA_ENCODING_UNKNOWN_FORMATA record from replica '%s' in the replication changelog of domain '%s' cannot be decoded because its format (%x) is invalidServerMessages.ERR_FILE_TRUSTMANAGER_INVALID_TYPEThe trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %sServerMessages.ERR_FULL_UPDATE_MISSING_REMOTECannot start total update in domain "%s" from this directory server DS(%s): cannot find remote directory server DS(%s)ServerMessages.ERR_INIT_EXPORTER_DISCONNECTIONDomain %s (server id: %s) : remote exporter server disconnection (server id: %s ) detected during initializationServerMessages.ERR_LDAP_PTA_MAPPED_BIND_FAILEDThe user "%s" could not be authenticated using LDAP PTA policy "%s" because the bind failed unexpectedly for the following reason: %sServerMessages.ERR_LDAP_PTA_MAPPED_SEARCH_FAILEDThe user "%s" could not be authenticated using LDAP PTA policy "%s" because the search failed unexpectedly for the following reason: %sServerMessages.ERR_LDAP_PTA_MAPPED_SEARCH_NO_CANDIDATESThe user "%s" could not be authenticated using LDAP PTA policy "%s" because the search did not return any entries matching the filter "%s"ServerMessages.ERR_LDAP_PTA_MAPPING_ATTRIBUTE_NOT_FOUNDThe user "%s" could not be authenticated using LDAP PTA policy "%s" because the following mapping attributes were not found in the user's entry: %sServerMessages.ERR_LDIF_BACKEND_DUPLICATE_ENTRYLDIF file %s configured for use with the LDIF backend defined in configuration entry %s has multiple entries with a DN of %sServerMessages.ERR_LDIF_BACKEND_ENTRY_OUT_OF_SCOPELDIF file %s configured for use with the LDIF backend defined in configuration entry %s includes entry %s which is not below the base DN defined for that backendServerMessages.ERR_LDIF_BACKEND_ERROR_CLOSING_FILEAn error occurred while trying to close file %s for the LDIF backend defined in configuration entry %s: %sServerMessages.ERR_LDIF_BACKEND_ERROR_CREATING_FILEAn error occurred while trying to create file %s to write an updated version of the data for the LDIF backend defined in configuration entry %s: %sServerMessages.ERR_LDIF_BACKEND_ERROR_WRITING_FILEAn error occurred while trying to write updated data to file %s for the LDIF backend defined in configuration entry %s: %sServerMessages.ERR_LDIF_BACKEND_MISSING_PARENTLDIF file %s configured for use with the LDIF backend defined in configuration entry %s contains entry %s but its parent entry has not yet been readServerMessages.ERR_LDIF_CONNHANDLER_CANNOT_RENAMEAn error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %sServerMessages.ERR_LDIF_COULD_NOT_BASE64_DECODE_DNUnable to parse LDIF entry starting at line %d because it was not possible to base64-decode the DN on line "%s": %sServerMessages.ERR_LDIF_COULD_NOT_EVALUATE_FILTERS_FOR_IMPORTAn error occurred while attempting to determine whether LDIF entry "%s" starting at line %d should be imported as a result of the include and exclude filter configuration: %sServerMessages.ERR_LDIF_INVALID_ATTR_OPTIONUnable to parse LDIF entry %s starting at line %d because it has an invalid binary option for attribute %sServerMessages.ERR_LDIF_INVALID_DNUnable to parse LDIF entry starting at line %d because an error occurred while trying to parse the value of line "%s" as a distinguished name: %sServerMessages.ERR_LDIF_MULTIPLE_VALUES_FOR_SINGLE_VALUED_ATTREntry %s starting at line %d includes multiple values for single-valued attribute %sServerMessages.ERR_LDIF_SCHEMA_VIOLATIONEntry %s read from LDIF starting at line %d is not valid because it violates the server's schema configuration: %sServerMessages.ERR_LOCAL_BACKEND_TAKES_PRECEDENCE_OVER_PROXY_BACKENDProxy backend '%s' is being deregistered from base DN %s because local backend '%s' is registering against it. Local backends take precedence over proxy backendsServerMessages.ERR_LOG_AGGREGATOR_MESSAGE_LOGGED_TOO_OFTENThe message with ID %d has been generated %d times in the last second: %sServerMessages.ERR_LOGGER_ERROR_ENFORCING_RETENTION_POLICYError occurred while enforcing retention policy %s for logger %s: %sServerMessages.ERR_LOGGER_ERROR_OPENING_FILEError occurred while opening log file %s for logger %s: %sServerMessages.ERR_MODIFY_ADD_DUPLICATE_VALUEEntry %s cannot be modified because it would have resulted in one or more duplicate values for attribute %s: %sServerMessages.ERR_MODIFY_ADD_INVALID_SYNTAX_NO_VALUEWhen attempting to modify entry %s, one value for attribute %s was found to be invalid according to the associated syntax: %sServerMessages.ERR_MODIFY_DELETE_MISSING_VALUESEntry %s cannot be modified because the attempt to update attribute %s would have removed one or more values from the attribute that were not present: %sServerMessages.ERR_MODIFY_INCREMENT_REQUIRES_INTEGER_VALUEEntry %s cannot be modified because an attempt was made to increment the value of attribute %s but the value "%s" could not be parsed as an integerServerMessages.ERR_MODIFY_REPLACE_INVALID_SYNTAX_NO_VALUEWhen attempting to modify entry %s to replace the set of values for attribute %s, one value was found to be invalid according to the associated syntax: %sServerMessages.ERR_PLUGIN_LDIF_IMPORT_PLUGIN_EXCEPTIONThe LDIF import plugin defined in configuration entry %s threw an exception when it was invoked on entry %s: %sServerMessages.ERR_PLUGIN_PWPIMPORT_ERROR_ENCODING_PASSWORDAn error occurred while attempting to encode a password value stored in attribute %s of user entry %s: %s. Password values for this user will not be encodedServerMessages.ERR_PLUGIN_REFERENT_ATTR_UNINDEXEDThe referential integrity plugin defined in configuration entry %s is configured to operate on attribute %s but there is no equality index defined for this attribute in backend %sServerMessages.ERR_PLUGIN_REFERENT_ENTRY_MISSINGThe entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not exist in any of the configured naming contextsServerMessages.ERR_PLUGIN_REFERENT_NAMINGCONTEXT_MISMATCHThe entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not belong to any of the configured naming contextsServerMessages.ERR_PLUGIN_UNIQUEATTR_ATTR_NOT_UNIQUEA unique attribute conflict was detected for attribute %s: value %s already exists in entry %sServerMessages.ERR_PLUGIN_UNIQUEATTR_ATTR_UNINDEXEDThe unique attribute plugin defined in configuration entry %s is configured to operate on attribute %s but there is no equality index defined for this attribute in backend %sServerMessages.ERR_PROXY_BACKEND_CANNOT_USE_BASE_DN_ALREADY_IN_USEProxy backend '%s' cannot register itself against base DN %s because this base DN is already registered against backend '%s'ServerMessages.ERR_PROXY_PARTITION_BASE_DN_MUST_BE_SUBORDINATESThe partition base DN '%s' should be subordinate to one of the base DNs %s of proxy backend '%s'ServerMessages.ERR_PROXY_PARTITION_BASE_DN_MUST_NOT_BE_SUBORDINATESThe partition base DN '%s' shouldn't be subordinate to one of the other partition base DNs %s of proxy backend '%s'ServerMessages.ERR_PWPOLICY_INVALID_PASSWORD_ATTRIBUTE_SYNTAXThe password policy definition contained in configuration entry "%s" is invalid because the specified password attribute "%s" has a syntax OID of %s. The password attribute must have a syntax OID of either 1.3.6.1.4.1.26027.1.3.1 (for the user password syntax) or 1.3.6.1.4.1.4203.1.1.2 (for the authentication password syntax)ServerMessages.ERR_PWPOLICY_NEW_VALIDATORS_OCThe subentry %s using the %s objectclass cannot define validators using the new %s objectclassServerMessages.ERR_PWPOLICY_NO_MIXING_OCSThe subentry %s cannot use both %s and %s objectclassesServerMessages.ERR_PWPOLICY_OLD_VALIDATOR_OCThe subentry %s using the %s objectclass cannot define validators using the old %s objectclassServerMessages.ERR_PWPOLICY_REJECT_DUE_TO_UNKNOWN_VALIDATOR_LOGThe password for user %s could not be validated because the password policy subentry %s is referring to an unknown password validator (%s). Please make sure the password policy subentry only refers to validators that exist on all replicasServerMessages.ERR_PWPOLICY_UNKNOWN_VALIDATORThe password policy definition contained in configuration entry "%s" is invalid because the password validator "%s" specified in attribute "%s" cannot be foundServerMessages.ERR_PWPSTATE_CANNOT_DECODE_BOOLEANUnable to decode value "%s" for attribute %s in user entry %s as a Boolean valueServerMessages.ERR_PWPSTATE_CANNOT_DECODE_SUBENTRY_VALUE_AS_DNAn error occurred while attempting to decode the ds-pwp-password-policy-dn value "%s" in user entry "%s" as a DN: %sServerMessages.ERR_RECEIVED_CHANGE_STATUS_NOT_FROM_DSReceived change status message does not come from a directory server (dn: %s, server id: %s, msg: %s)ServerMessages.ERR_RECURRINGTASK_CANNOT_LOAD_CLASSAn error occurred while attempting to load class %s specified in attribute %s of the provided recurring task entry: %s. Does this class exist in the Directory Server classpath?ServerMessages.ERR_REFRESHING_KEY_MANAGER_PROVIDERFile based key manager provider '%s' cannot load content from keystore file '%s'. TLS connections which rely on this key manager provider may fail. Restarting the server or the impacted connection handler may resolve this problem. Error detail: %sServerMessages.ERR_REFRESHING_TRUST_MANAGER_PROVIDERFile based trust manager provider '%s' cannot load content from truststore file '%s'. TLS connections which rely on this trust manager provider may fail. Restarting the server or the impacted connection handler may resolve this problem. Error detail: %sServerMessages.ERR_REGEXMAP_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINThe processed ID string %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'ServerMessages.ERR_REGISTER_BASEDN_ALREADY_EXISTSUnable to register base DN %s with the Directory Server for backend %s because that base DN is already registered for backend %sServerMessages.ERR_REGISTER_BASEDN_DIFFERENT_PARENT_BASESUnable to register base DN %s with the Directory Server for backend %s because that backend already contains another base DN %s that is not subordinate to the same base DN in the parent backendServerMessages.ERR_REGISTER_BASEDN_HIERARCHY_CONFLICTUnable to register base DN %s with the Directory Server for backend %s because that backend already contains another base DN %s that is within the same hierarchical pathServerMessages.ERR_REGISTER_BASEDN_NEW_BASE_NOT_SUBORDINATEUnable to register base DN %s with the Directory Server for backend %s because that backend already contains one or more other base DNs that are subordinate to backend %s but the new base DN is notServerMessages.ERR_REMOTE_EXPORTER_IDLEInitialization of domain '%s' interrupted: no data received from the remote exporter '%s' for %sServerMessages.ERR_RESET_GENERATION_CONN_ERR_IDFor replicated domain %s, in server with serverId=%s, the generation ID could not be set to value %s in the rest of the topology because this server is NOT connected to any replication server. You should check in the configuration that the domain is enabled and that there is one replication server up and runningServerMessages.ERR_ROOTDSE_INVALID_SEARCH_BASEUnwilling to perform a search (connection ID %d, operation ID %d) with a base DN of "%s" in the root DSE backend. The base DN for searches in this backend must be the DN of the root DSE itselfServerMessages.ERR_ROOTDSE_INVALID_SEARCH_SCOPEUnable to process the search with connection ID %d and operation ID %d because it had an invalid scope of %sServerMessages.ERR_RS_DURING_HANDSHAKEReplication server %s was attempting to connect to replication server %s but an error occurred in handshake phase. Error: %sServerMessages.ERR_RS_INVALID_INIT_STATUSReplication server received invalid initial status: %s for replication domain %s from server id %sServerMessages.ERR_RS_INVALID_NEW_STATUSReceived invalid new status %s in RS for replication domain %s and directory server id %sServerMessages.ERR_SASL_CANNOT_DECODE_USERNAME_AS_DNAn error occurred while attempting to decode the SASL %s username "%s" because it appeared to contain a DN but DN decoding failed: %sServerMessages.ERR_SASL_CANNOT_GET_ENTRY_BY_DNAn error occurred while attempting to retrieve user entry %s as specified in the DN-based username of a SASL %s bind request: %sServerMessages.ERR_SASL_CANNOT_GET_REVERSIBLE_PASSWORDSAn error occurred while attempting to retrieve the clear-text password(s) for user %s in order to perform SASL %s authentication: %sServerMessages.ERR_SASL_CANNOT_GET_SCRAM_CREDENTIALSAn error occurred while attempting to retrieve the SCRAM credentials for user '%s' in order to perform SASL %s authentication: %sServerMessages.ERR_SATUACM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINThe certificate with subject %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'ServerMessages.ERR_SATUACM_NO_SUCH_ATTRMapping %s in configuration entry %s references attribute %s which is not defined in the server schemaServerMessages.ERR_SCHEMA_CANNOT_FIND_CONCAT_FILEUnable to find a file containing concatenated schema element definitions in order to determine if any schema changes were made with the server offline. The file was expected in the %s directory and should have been named either %s or %sServerMessages.ERR_SDTUACM_MULTIPLE_MATCHING_ENTRIES_FOR_ADMINThe certificate with subject %s could not be mapped to exactly one user. It maps at least to both '%s' and '%s'ServerMessages.ERR_SECRET_FILE_CANNOT_BE_DECODED'%s' cannot decode the secret file '%s': %sCould not retrieve auto-configuration data from directory server '%s' for replication server group '%s'. Exception : %s"Could not retrieve the list of replicas from replication server '%s' for replication server group '%s'. Exception : %sServerMessages.ERR_SETUP_ACCESSING_KEYSTORECould not access the %s keystore '%s'. Check that the content of the file corresponds to a valid keystore, that you have access rights to it and that a valid password has been provided if needed. Error details: %sServerMessages.ERR_SETUP_ACCESSING_KEYSTORE_ENTRIESCould not read the %s keystore '%s' entries. Check that the content of the file corresponds to a valid keystore, that you have access rights to it and that a valid password has been provided if needed. Error details: %sServerMessages.ERR_SETUP_ACCESSING_TRUSTSTORECould not access the %s truststore '%s'. Check that the content of the file corresponds to a valid truststore, that you have access rights to it and that a valid password has been provided if needed. Error details: %sServerMessages.ERR_SETUP_COPY_FILEAn error occurred while copying file '%s' into '%s': '%s'ServerMessages.ERR_SETUP_DS_PROFILE_CONF_METHOD_NOT_FOUNDError in profile '%s': the default value for parameter '%s' cannot be derived from the SetupConfiguration method '%s' because no such method existsServerMessages.ERR_SETUP_DS_PROFILE_PARAMETER_WITH_PROFILE_NOT_PROVIDEDSetup profile parameter '%s' references the profile '%s' which has not been provided on the command line. Setup profiles can be added on the command line with the '%s' optionServerMessages.ERR_SETUP_INVALID_ADMIN_PORTAdministration connector port '%d' is not in allowed range %d, %dServerMessages.ERR_SETUP_INVALID_HTTP_PORTHTTP port '%d' is not in allowed range %d, %dServerMessages.ERR_SETUP_INVALID_HTTPS_PORTHTTPS port '%d' is not in allowed range %d, %dServerMessages.ERR_SETUP_INVALID_LDAP_PORTLDAP port '%d' is not in allowed range %d, %dServerMessages.ERR_SETUP_INVALID_LDAPS_PORTLDAPS port '%d' is not in allowed range %d, %dServerMessages.ERR_SETUP_INVALID_PORTPort '%d' is not in allowed range %d, %dServerMessages.ERR_SETUP_INVALID_REPLICATION_PORTReplication port '%d' is not in allowed range %d, %dServerMessages.ERR_SETUP_PROFILE_ENCODE_PWD_PARAMETER_VALUEUnable to encode password associated to parameter '%s' of profile '%s' (%s)ServerMessages.ERR_SETUP_PROFILE_INVALID_PWD_PARAMETER_VALUEThe value for password parameter '%s' of profile '%s' is invalid (%s)ServerMessages.ERR_SETUP_PROFILE_RESOURCE_SUBSTITUTIONAn error occurred while substituting properties from profile '%s' resource file '%s': %sServerMessages.ERR_SMTP_ASNH_CANNOT_SEND_MESSAGEAn error occurred while attempting to send an account status notification message for notification type %s for user entry %s: %sServerMessages.ERR_SMTP_ASNH_SUBJECT_INVALID_NOTIFICATION_TYPEUnable to parse message subject value '%s' from configuration entry '%s' because '%s' is not a valid account status notification typeServerMessages.ERR_SMTP_ASNH_TEMPLATE_CANNOT_PARSEAn error occurred while attempting to parse message template file '%s' referenced in configuration entry '%s': %sServerMessages.ERR_SMTP_ASNH_TEMPLATE_INVALID_NOTIFICATION_TYPEUnable to parse message template file path value '%s' from configuration entry '%s' because '%s' is not a valid account status notification typeServerMessages.ERR_SMTP_ASNH_TEMPLATE_UNDEFINED_ATTR_TYPEThe notification-user-attr token starting at column %d of line %d references undefined attribute type %sServerMessages.ERR_SMTP_ASNH_TEMPLATE_UNDEFINED_PROPERTYThe notification-property token starting at column %d of line %d references undefined notification property %sServerMessages.ERR_SMTP_ASNH_TEMPLATE_UNRECOGNIZED_TOKENAn unrecognized token %s was found at column %d of line %dServerMessages.ERR_STARTOK_CANNOT_RENAMEAn error occurred while attempting to rename file %s to %s for use as the ".startok" configuration file: %sServerMessages.ERR_STARTOK_CANNOT_WRITEAn error occurred while attempting to copy the current configuration from file %s into temporary file %s for use as the ".startok" configuration file: %sServerMessages.ERR_STATE_VERSION_IS_NEWERThe backend '%s' data format is incompatible with the version of this server, which may be due to an attempt to restore a backup from a more recent version of the server. Please upgrade this server to a newer version. The backend data has format version '%s' whereas this server supports format version '%s".ServerMessages.ERR_TASK_ADDSCHEMAFILE_ERROR_CHECKING_FOR_FILEUnable to add one or more files to the server schema because an error occurred while attempting to determine whether file %s exists in schema directory %s: %sServerMessages.ERR_TASKSCHED_CANNOT_LOAD_CLASSAn error occurred while attempting to load class %s specified in attribute %s of the provided task entry: %s. Does this class exist in the Directory Server classpath?ServerMessages.ERR_TASKSCHED_CANNOT_PARSE_ENTRY_FATALAn error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is an unrecoverable error, and parsing cannot continueServerMessages.ERR_TASKSCHED_CANNOT_PARSE_ENTRY_RECOVERABLEAn error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is not a fatal error, so the task scheduler will attempt to continue parsing the file and schedule any additional tasks that it containsServerMessages.ERR_TASKSCHED_CANNOT_RENAME_NEW_BACKING_FILEAn error occurred while attempting to rename the new tasks backing file from %s to %s: %s. If the Directory Server is restarted, then the task scheduler may not work as expectedServerMessages.ERR_UNCAUGHT_WORKER_THREAD_EXCEPTION%s encountered an uncaught exception while processing operation %s: %sServerMessages.ERR_UNROUTABLE_MESSAGE_BECAUSE_ROUTING_TABLE_IS_EMPTY%s in Replication Server=%s, an initialization message of type %s cannot be sent to its destination server. Details: routing table is emptyServerMessages.ERR_UNROUTABLE_MESSAGE_CAUSED_BY_EXCEPTION%s message of type %s cannot be routed. Details: %sServerMessages.ERR_UNROUTABLE_MESSAGE_INITIALIZE_ALL%s for domain %s cannot route message of type %s to all the replicas in the topology because none are reachableServerMessages.ERR_UPGRADE_COPY_OPENDMK_JAR_FILE_TO_EXTLIBAn error occurred while copying OpenDMK jar file '%s' to '%s': %sServerMessages.ERR_UPGRADE_INVALID_SEQUENCE_FOR_TASKS_VERSIONInvalid sequence for task version: task %s tried to register for version %s but the previous task used a higher version: %s. This suggests there is a copy/paste error in the version numberServerMessages.ERR_UPGRADE_TASK_CANNOT_RENAME_FILEThe file '%s' could not be renamed to '%s': %sServerMessages.ERR_VERIFY_DN2ID_WRONG_IDFile dn2id has ID %d instead of %d for key %sServerMessages.ERR_VERIFY_ID2COUNT_WRONG_COUNTFile id2childrenCount has wrong number of children for DN <%s> (got %d, expecting %d)ServerMessages.ERR_VIRTUAL_STATIC_GROUP_CANNOT_DECODE_TARGETUnable to decode "%s" as the target DN for group %s: %sServerMessages.ERR_WORKER_THREAD_LEAKED_OPENTELEMETRY_CONTEXT_IN_TLS_AFTERWorker thread '%s': after executing request '%s', an OpenTelemetry context is still present in thread-local storage while it should not. This indicates a context leak: some code is not properly closing the OpenTelemetry Scope. Check the code and make sure to use a try-with-resources where the scope is used. Leaked context is: '%s'ServerMessages.INFO_CHANGELOG_LOG_FILE_RECOVEREDLog file '%s' was successfully recovered by removing unreadable records. The file changed size from %d to %d bytes.ServerMessages.INFO_DSREPL_START_INITIALIZATION_FROM_OR_TO_SINGLE_REMOTEStarting initialization from '%s' to '%s' for base DNs: %sServerMessages.INFO_GENERATING_STACK_DUMPGenerating stack dump, sample number : %d using %s for pid %dServerMessages.INFO_PROXY_BASE_DNS_REGISTRATION_CHANGEProxy backend '%s' automatically registered itself against the base DNs %s. It was previously registered against the base DNs %sServerMessages.INFO_REPLICA_COMPUTING_GENERATION_IDDirectory server DS(%s) did not find a generation ID for domain '%s'. A new generation ID will be computed by exporting the first %d entries in the domainServerMessages.INFO_SSL_SERVER_CON_ATTEMPT_ERRORReplication server accepted a connection from %s to local address %s but the SSL handshake failed. This is probably benign, but may indicate a transient network outage or a misconfigured client application connecting to this replication server. The error was: %sServerMessages.INFO_TASK_TOOL_TASK_SCHEDULED_FUTURE%s task %s scheduled to start %sServerMessages.INFO_TEMPORARILY_UNREACHABLE_SERVERThe server '%s' may retry the initialization process because the server '%s' in domain '%s' is temporarily unreachableServerMessages.INFO_TIME_IN_HOURS_MINUTES_SECONDS%d hours, %d minutes, %d secondsServerMessages.NOTE_BAD_DATA_IN_FULL_UPDATEIgnoring reset generation ID request from '%s' to '%s' for replica '%s' because the replica is being re-initializedServerMessages.NOTE_CONFIG_BACKEND_ACTION_REQUIRED_TO_CHANGE_CLASSThe requested change to configuration entry %s would cause the class for the associated backend to change from %s to %s. This change will not take effect until the backend is disabled and re-enabled, or until the Directory Server is restartedServerMessages.NOTE_DIRECTORY_SERVER_CHANGED_STATUSDirectory server DS(%s) for domain "%s" has changed its status to %sServerMessages.NOTE_DIRECTORY_SERVER_STARTING%s (build %s, revision number %s) starting upServerMessages.NOTE_DISK_SPACE_RESTOREDThe free space (%s) on the disk containing directory "%s" is now above the low threshold for the following subsystems: %sServerMessages.NOTE_DS_NOTIFIED_STATE_IS_BAD_DATA_GEN_IDThis replica `%s` has received a notification from its replication server `%s` to stop processing updates for domain `%s` as part of a disaster recovery procedure. This replica must be reinitialized as part of the recovery procedureServerMessages.NOTE_EXPORT_PROGRESS_REPORTExported %d records and skipped %d (recent rate %.1f/sec)ServerMessages.NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_ALLFinished total update: exported domain "%s" from this directory server DS(%s) to all remote directory servers. %sServerMessages.NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_ALLStarting total update: exporting %d entries in domain "%s" from this directory server DS(%s) to all remote directory serversServerMessages.NOTE_FULL_UPDATE_ENGAGED_FROM_REMOTE_STARTStarting total update: importing domain "%s" from remote directory server DS(%s) to this directory server DS(%s)ServerMessages.NOTE_IMPORT_LDIF_INDEX_STARTEDIndex %s phase two started processing %d buffers in %d batchesServerMessages.NOTE_IMPORT_PHASE_STATSTotal import time was %d seconds. Phase one processing completed in %d seconds, phase two processing completed in %d secondsServerMessages.NOTE_IMPORT_STARTING%s starting import (build %s, R%s)ServerMessages.NOTE_JVM_HOST_WITH_UNKNOWN_PHYSICAL_MEMJVM Host: %s, running %s, unknown physical memory size, number of processors available %dServerMessages.NOTE_PROXY_SERVICE_DISCOVERY_CHANGEDService discovery mechanism has changed from '%s' to '%s' for proxy backend '%s'. The existing connections are being closed immediatelyServerMessages.NOTE_READER_IO_EXCEPTIONAn I/O error occurred while reading replication messages from %s. The connection will close and replication server (%s) will not process any more updates from it. Reported error is: %sServerMessages.NOTE_REBUILD_FINAL_STATUSRebuild complete. Processed %d entries in %d seconds (average rate %.1f/sec)ServerMessages.NOTE_REPLICATION_SERVER_LISTENINGReplication server RS(%s) started listening for new connections on address %s port %dServerMessages.NOTE_RS_HAS_GROUP_WITH_LOWER_PRIORITYRS(%s) groupId '%s' has lower priority than groupId '%s' which matched at least one other RSServerMessages.NOTE_RS_HAS_NO_GENERATION_IDRS(%s) has no generation Id, but at least one other RS has the same generation Id %s as DS(%s)ServerMessages.NOTE_TASK_FINISHED%s task %s finished execution in the state %sServerMessages.NOTE_UNRESOLVED_CONFLICT_ADD_EXISTSAn unresolved conflict was detected in CSN %s replaying an ADD of "%s" which already exists (adding as "%s"). Consider reviewing both entries and either merge the contents manually or delete oneServerMessages.NOTE_UNRESOLVED_CONFLICT_ADD_NO_PARENTAn unresolved conflict was detected in CSN %s replaying an ADD of "%s" as the parent entry is missing (adding as "%s"). Consider restoring the parent entry, or deleting the new entryServerMessages.NOTE_UNRESOLVED_CONFLICT_RENAME_NO_PARENTAn unresolved conflict was detected in CSN %s replaying a MODIFYDN of "%s" as the new parent entry "%s" does not exist. Consider restoring the parent entry, or deleting this entryServerMessages.WARN_ACI_ADD_LIST_FAILED_DECODE"%s", located in the entry "%s", because of the following reason: %sServerMessages.WARN_ACI_ERROR_CHECKING_CANONICAL_HOSTNAMEAn error occurred while attempting to determine whether hostname %s referenced in dns expression bind rule "%s" used the correct canonical representation: %s. This likely means that the provided hostname will never match any clientsServerMessages.WARN_ACI_LOCALHOST_DOESNT_MATCH_CANONICAL_VALUEThe provided Access Control Instruction (ACI) bind rule dns expression value "%s" references hostname %s, but the canonical representation for that hostname is configured to be %s. The server will attempt to automatically interpret the correct localhost valueServerMessages.WARN_ACI_SYNTAX_ILLEGAL_CHAR_IN_NUMERIC_OIDThe provided Access Control Instruction (ACI) targetcontrol OID value "%s" could not be parsed because the value contained an illegal character %c at position %dServerMessages.WARN_ADD_OP_INVALID_SYNTAX_NO_VALUEEntry "%s" contains a value for attribute %s that is invalid according to the syntax for that attribute: %sServerMessages.WARN_CANNOT_PARSE_ENV_VARIABLE_FOR_SMALL_DB_SIZEProperty '%s' contains value '%s' which cannot be parsed as a long. Defaulting to '%s' bytes for small DB sizeServerMessages.WARN_CANNOT_READ_SECRET_FILE'%s' cannot read the secret file '%s': %sServerMessages.WARN_CHANGELOG_SERVER_UNKNOWN_HOSTDirectory server DS(%s) was unable to connect to replication server at %s for domain '%s': unknown hostServerMessages.WARN_CONFIG_SCHEMA_CANNOT_OPEN_FILESchema configuration file %s in directory %s cannot be parsed because an unexpected error occurred while trying to open the file for reading: %sServerMessages.WARN_CONFIG_SCHEMA_CANNOT_READ_LDIF_ENTRYSchema configuration file %s in directory %s cannot be parsed because an unexpected error occurred while trying to read its contents as an LDIF entry: %sServerMessages.WARN_COULD_NOT_FIND_CHANGELOGDirectory server DS(%s) was unable to connect to any of the following replication servers for domain "%s": %sServerMessages.WARN_DS_DISCONNECTED_DURING_HANDSHAKEA transient problem occurred while Directory Server %s was connecting to this Replication Server %s. The peer server may try to establish a connection again. The problem was: %sServerMessages.WARN_DS_DURING_HANDSHAKE_UNEXPECTED_MESSAGEDirectory server %s stopped the handshake process with replication server %s because it received the unexpected message '%s'ServerMessages.WARN_EXACTMAP_ATTR_UNINDEXEDThe exact match identity mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %sServerMessages.WARN_EXTOP_PASSMOD_CANNOT_UPDATE_PWP_STATEAn error occurred while attempting to update the password policy state information for user %s as part of a password modify extended operation (result code='%s', error message='%s')ServerMessages.WARN_GROUP_FILTER_NOT_INDEXEDThe search filter "%s" used by group implementation %s is not indexed in backend %s. Backend initialization for this group implementation might take a very long time to completeServerMessages.WARN_HOLE_IN_CHANGELOGChangelog file '%s' has missing data between keys '%s' and '%s'. When the two keys are CSNs, this indicates a hole in the changelog. The server may have missed changes and may need to be re-initialized. Verify the changelog in the originating server.ServerMessages.WARN_MULTIPLE_PWD_POLICY_SUBENTRIESFound %d conflicting password policy subentries for user %s, used %sServerMessages.WARN_NO_CHANGELOG_SERVER_LISTENINGDirectory server DS(%s) was unable to connect to replication server %s for domain "%s". Please check that there is a replication server listening at this addressServerMessages.WARN_PROXY_NO_FAILOVER_ONLY_PRIMARY_SERVERS_DISCOVEREDProxy backend '%s' cannot failover: only primary servers have been discovered via the service discovery mechanism '%s'. Primary servers are %sServerMessages.WARN_PROXY_NO_FAILOVER_ONLY_SECONDARY_SERVERS_DISCOVEREDProxy backend '%s' cannot failover: only secondary servers have been discovered via the service discovery mechanism '%s'. Secondary servers are %sServerMessages.WARN_PROXY_SERVER_UNAVAILABLEThe server '%s' for proxy backend '%s' is unavailable. The last failure that prevented the server from being used was: %sServerMessages.WARN_REGEXMAP_ATTR_UNINDEXEDThe regular expression identity mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %sServerMessages.WARN_REGISTER_BASEDN_ENTRIES_IN_MULTIPLE_BACKENDSBackend %s already contains entry %s which has just been registered as the base DN for backend %s. These conflicting entries can cause unexpected or errant search results, and both backends should be reinitialized to ensure that each has the correct contentServerMessages.WARN_REPLICATION_DELAY_ABOVE_HEALTH_THRESHOLDReplication delay for '%s' is above %dms, current delay: %dmsServerMessages.WARN_RS_DISCONNECTED_DURING_HANDSHAKEA transient problem occurred while Replication Server %s was connecting to this Replication Server %s. The Replication Server should try to reconnect later. The problem was: %sServerMessages.WARN_SATUACM_ATTR_UNINDEXEDThe subject attribute to user attribute certificate mapper defined in configuration entry %s references attribute type %s which does not have an equality index defined in backend %sServerMessages.WARN_SECRET_FILE_NOT_SUITABLE_FOR_PURPOSE'%s' has ignored the file '%s' either because the certificate does not contain the key usage extension '%s', or because the file does not contain the appropriate key typesCannot connect to replica '%s' for replication service discovery mechanism '%s'. The replica entry is: %sServerMessages.WARN_SMTPALERTHANDLER_ERROR_SENDING_MESSAGEAn error occurred when trying to send an e-mail message for administrative alert with type %s and message %s: %sServerMessages.WARN_TASKSCHED_CANNOT_RENAME_CURRENT_BACKING_FILEAn error occurred while attempting to rename the current tasks backing file from %s to %s: %s. The previous task configuration (which does not reflect the latest update) may be lostServerMessages.WARN_TIMEOUT_CONNECTING_TO_RSDirectory server DS(%s) timed out while connecting to replication server %s for domain "%s"ServerMessages.WARN_TRANSIENT_SOCKET_PROBLEMA transient problem occurred while DS(%s) was connecting to RS(%s), Directory Server will try to connect again. Problem was: %sServerMessages.WARN_UNINDEXED_INTERNAL_SEARCHThe server is performing an unindexed internal search request with base DN '%s', scope '%s', and filter '%s'. Unindexed internal searches are usually unexpected and could impact performance. Please verify that this backend's indexes are configured correctly for these search parametersServerMessages.WARN_UPGRADE_CANNOT_FIND_TASK_BACKEND_FILEUnable to find the task backend file location in the configuration file %s, entry '%s' or attribute '%s' is missingConfiguration attribute %s has distinct values in replication domain configuration entries. Migration to replication synchronization provider configuration will keep only one value, '%s' and discarded '%s' -
Uses of LocalizableMessageDescriptor.Arg3 in org.opends.server.extensions
Methods in org.opends.server.extensions with parameters of type LocalizableMessageDescriptor.Arg3Modifier and TypeMethodDescriptionstatic voidIndexedAttributesChecks.checkAllAttributesAreIndexedForEquality(Dn cfgDn, Set<Dn> cfgBaseDNs, Collection<AttributeType> attrTypes, LocalizableMessageDescriptor.Arg3<Object, Object, Object> notIndexedMsg, ConfigChangeResult ccr, BackendConfigManager backendConfigManager) Checks whether all the attribute types are indexed for equality. -
Uses of LocalizableMessageDescriptor.Arg3 in org.opends.server.types
Methods in org.opends.server.types with parameters of type LocalizableMessageDescriptor.Arg3Modifier and TypeMethodDescriptionprotected voidOperation.checkAttributeConformsToSyntax(Entry entry, Attribute attribute, LocalizableMessageDescriptor.ArgN invalidSyntaxErrorMsg, LocalizableMessageDescriptor.Arg3<Object, Object, Object> invalidSyntaxNoValueErrorMsg, LocalizableMessageDescriptor.Arg1<Object> rejectErrorMsg) Checks whether an attribute's values conform to its syntax.