Uses of Class
org.forgerock.i18n.LocalizableMessageDescriptor.Arg4
Packages that use LocalizableMessageDescriptor.Arg4
Package
Description
This package provides an alternative localization mechanism to
org.slf4j.cal10n.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.
-
Uses of LocalizableMessageDescriptor.Arg4 in org.forgerock.i18n.slf4j
Methods in org.forgerock.i18n.slf4j with parameters of type LocalizableMessageDescriptor.Arg4Modifier and TypeMethodDescription<T1,T2, T3, T4>
voidLocalizedLogger.error(LocalizableMessageDescriptor.Arg4<T1, T2, T3, T4> d, T1 a1, T2 a2, T3 a3, T4 a4) Logs an error message.<T1,T2, T3, T4>
voidLocalizedLogger.info(LocalizableMessageDescriptor.Arg4<T1, T2, T3, T4> d, T1 a1, T2 a2, T3 a3, T4 a4) Logs a message at INFO level.<T1,T2, T3, T4>
voidLocalizedLogger.note(LocalizableMessageDescriptor.Arg4<T1, T2, T3, T4> d, T1 a1, T2 a2, T3 a3, T4 a4) Logs a message at NOTICE level.<T1,T2, T3, T4>
voidLocalizedLogger.warn(LocalizableMessageDescriptor.Arg4<T1, T2, T3, T4> d, T1 a1, T2 a2, T3 a3, T4 a4) Logs a warning message. -
Uses of LocalizableMessageDescriptor.Arg4 in org.opends.messages
Fields in org.opends.messages declared as LocalizableMessageDescriptor.Arg4Modifier and TypeFieldDescriptionServerMessages.DEBUG_ERROR_UPDATING_RUVError %s when updating server state %s : %s base dn : %sServerMessages.ERR_CANNOT_ADD_CONFLICT_ATTRIBUTEA conflict was detected but the conflict information could not be added to entry %s. Conflict with %s %s, Result: %sServerMessages.ERR_CHANGELOG_UNABLE_TO_CREATE_REPLICA_DBCould not get or create replica DB for base DN '%s', serverId '%s', generationId '%s': %sServerMessages.ERR_DIFFERENT_DATA_SET_NEED_RESYNCThe Directory server DS(%s) and Replication server RS(%s) are working on different dataset regarding the domain '%s' : the Directory server DS(%s) will reject all modification operations and must be re-initializedServerMessages.ERR_DS_BADLY_DISCONNECTEDThe connection from this replication server RS(%s) to directory server DS(%s) at %s for domain "%s" has failedServerMessages.ERR_DS_CANNOT_CHANGE_STATUSCould not compute new status in DS replication domain %s with server id %s. Was in %s status and received %s eventServerMessages.ERR_DSREPL_MIGRATION_CANNOT_ADD_RS_TO_REPL_DOMAINCannot add '%s' to the configuration of replication domain '%s' on server '%s'. The error was: %sServerMessages.ERR_DSREPL_MIGRATION_CANNOT_READ_SERVER_IDCannot read server ID from server '%s' on DNs '%s' and '%s'. The errors were: %sServerMessages.ERR_DUPLICATE_REPLICATION_SERVER_IDDuplicate server IDs found: replication server '%s' tried to connect from '%s', but replication server '%s' is already connected from '%s'. Make sure the two replication servers are configured with different server IDsServerMessages.ERR_ERROR_SEARCHING_RUVError %s when searching for server state %s : %s base dn : %sServerMessages.ERR_EXCEPTION_REPLAYING_OPERATIONAn Exception was caught while replaying operation %s %s (%s) : %sServerMessages.ERR_EXCEPTION_SENDING_TOPO_INFOCaught IOException while sending topology info (for update) on domain %s for %s server %s : %sServerMessages.ERR_EXCEPTION_STARTING_SESSION_PHASEDirectory server DS(%s) encountered an unexpected error while connecting to replication server %s for domain "%s": %sServerMessages.ERR_INVALID_IMPORT_SOURCEOn domain %s, initialization of server with serverId:%s has been requested from a server with an invalid serverId:%s. %sServerMessages.ERR_LDAP_PTA_MAPPED_SEARCH_TOO_MANY_CANDIDATESThe user "%s" could not be authenticated using LDAP PTA policy "%s" because the search of base DN "%s" returned more than one entry matching the filter "%s"ServerMessages.ERR_LDIF_BACKEND_ERROR_RENAMING_FILEAn error occurred while attempting to rename file %s to %s while writing updated data for the LDIF backend defined in configuration entry %s: %sServerMessages.ERR_LDIF_COULD_NOT_BASE64_DECODE_ATTRUnable to parse LDIF entry %s starting at line %d because it was not possible to base64-decode the attribute on line "%s": %sServerMessages.ERR_LDIF_INVALID_URLUnable to parse LDIF entry %s starting at line %d because the value of attribute %s was to be read from a URL but the URL was invalid: %sServerMessages.ERR_LOOP_REPLAYING_OPERATIONA loop was detected while replaying operation: %s %s (%s) error %sServerMessages.ERR_NO_KEY_MANAGER_CREATEDFile based key manager provider '%s' failed to load content from file '%s'. TLS connections which rely on this key manager provider may fail. Ensure that keystore file contains at least one private key compatible with the security providers. Security providers available in the running JVM are '%s'. The security provider used for loading key manager will be the first in the list which is compatible with the algorithm '%s'ServerMessages.ERR_NO_TRUST_MANAGER_CREATEDFile based trust manager provider '%s' failed to load content from file '%s'. TLS connections which rely on this trust manager provider may fail. Ensure that truststore file contains at least one private key compatible with the security providers. Security providers available in the running JVM are '%s'. The security provider used for loading trust manager will be the first in the list which is compatible with the algorithm '%s'ServerMessages.ERR_NO_X509_EXTENDED_KEY_MANAGER_AVAILABLEFile based key manager provider '%s' cannot load an X509 extended key manager from keystore file '%s'. TLS connections which rely on this key manager provider may fail. Security providers available in the running JVM are %s. The security provider used for loading key manager will be the first in the list which is compatible with the algorithm '%s'ServerMessages.ERR_NO_X509_EXTENDED_TRUST_MANAGER_AVAILABLEFile based trust manager provider '%s' cannot load an X509 extended trust manager from truststore file '%s'. TLS connections which rely on this trust manager provider may fail. Security providers available in the running JVM are %s. The security provider used for loading trust manager will be the first in the list which is compatible with the algorithm '%s'ServerMessages.ERR_PLUGIN_POST_CONNECT_PLUGIN_EXCEPTIONThe post-connect plugin defined in configuration entry %s threw an exception when it was invoked for connection %d from %s: %s. The connection will be terminatedServerMessages.ERR_PLUGIN_POST_DISCONNECT_PLUGIN_EXCEPTIONThe post-disconnect plugin defined in configuration entry %s threw an exception when it was invoked for connection %d from %s: %sServerMessages.ERR_PLUGIN_REFERENT_ATTR_MATCHING_RULE_UNINDEXEDThe referential integrity plugin defined in configuration entry %s is configured to operate on attribute %s but there is no %s extensible matching rule index defined for this attribute in backend %sServerMessages.ERR_PLUGIN_REFERENT_FILTER_MISMATCHThe entry referenced by the value '%s' of the attribute '%s' in the entry '%s' does not match the filter '%s'ServerMessages.ERR_PLUGIN_SUBORDINATE_DELETE_PLUGIN_EXCEPTIONThe subordinate delete plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminatedServerMessages.ERR_PLUGIN_SUBORDINATE_MODIFY_DN_PLUGIN_EXCEPTIONThe subordinate modify DN plugin defined in configuration entry %s threw an exception when it was invoked for connection %d operation %d: %s. Processing on this operation will be terminatedServerMessages.ERR_PWPSTATE_CANNOT_DECODE_GENERALIZED_TIMEAn error occurred while attempting to decode value "%s" for attribute %s in user entry %s in accordance with the generalized time format: %sServerMessages.ERR_RS_BADLY_DISCONNECTEDThe connection from this replication server RS(%s) to replication server RS(%s) at %s for domain "%s" has failedServerMessages.ERR_RS_CANNOT_CHANGE_STATUSCould not compute new status in RS replication domain %s for server id %s. Was in %s status and received %s eventServerMessages.ERR_SETUP_DS_INVALID_PROFILE_PARAM_VALUEThe value '%s' for parameter '%s' in profile '%s' is invalid. Please provide a value having the following syntax: %sServerMessages.ERR_SETUP_DS_PROFILE_CONF_METHOD_CALLEDError in profile '%s': the default value for parameter '%s' cannot be derived from the SetupConfiguration method '%s' because the method invocation threw an error: %sServerMessages.ERR_SETUP_INSTANCE_LOC_FILE_FOUNDThe file '%s' is referring to an invalid instance (%s). You must remove this file before setting up a new instance in the directory %s. Please use either the --%s option in non interactive mode or the interactive mode to setup an instance elsewhereServerMessages.ERR_SETUP_PROFILE_INVALID_DOMAIN_PARAMETER_VALUEThe value '%s' for domain parameter '%s' of profile '%s' is invalid (%s)ServerMessages.ERR_SETUP_PROFILE_INVALID_ENUM_PARAMETER_VALUEThe value '%s' for parameter '%s' in profile '%s' is invalid because it does not match any allowed values (%s)ServerMessages.ERR_SETUP_PROFILE_LOG_DSCONFIG'%s' setup profile failed to update server configuration file, dsconfig tool options: '%s'. Exception message:'%s'. Tool output: %sServerMessages.ERR_VERIFY_BIGINDEX_COUNT_WRONG_COUNTCounter of %s reports wrong number of entries for key <%s> (got %d, expecting %d)ServerMessages.ERR_WRITER_CHANGELOG_CURSOR_ABORTED_FOR_REMOTE_DSThe directory server %s can no longer keep up with changes coming from replication server %s for base DN %s. Some missing changes have been purged by this replication server and the connection will be terminated. The directory server may fail-over to another replication server that has not purged the changes that it needs. If there is no replication server containing the missing changes then it will fail to connect to any replication server and will need to be reinitialized. (Underlying error is: %s)ServerMessages.ERR_WRITER_CHANGELOG_CURSOR_ABORTED_FOR_REMOTE_RSThe replication server %s can no longer keep up with changes coming from replication server %s for base DN %s. Some missing changes have been purged by this replication server and the connection will be terminated. The directory servers connected to this replication server may fail-over to another replication server that has not purged the changes that it needs. If there is no replication server containing the missing changes then the directory servers will fail to connect to any replication server and will need to be reinitialized. (Underlying error is: %s)ServerMessages.INFO_CONFIG_CHANGE_RESULT_MESSAGES%s.%s succeeded but generated the following messages for entry %s: %sServerMessages.INFO_PROXY_FAILOVER_EFFECTIVEProxy backend '%s' successfully configured failover via the service discovery mechanism '%s': primary servers are %s and secondary servers are %sServerMessages.INFO_REPLICATION_SERVER_CONNECTION_FROM_DSReplication server RS(%s) has accepted a connection from directory server DS(%s) for domain "%s" at %sServerMessages.INFO_REPLICATION_SERVER_CONNECTION_FROM_RSReplication server RS(%s) has accepted a connection from replication server RS(%s) for domain "%s" at %sServerMessages.INFO_REPLICATION_SERVER_CONNECTION_TO_RSReplication server RS(%s) has connected to replication server RS(%s) for domain "%s" at %sServerMessages.INFO_TIME_IN_DAYS_HOURS_MINUTES_SECONDS%d days, %d hours, %d minutes, %d secondsServerMessages.NOTE_ERRORLOG_ACCTNOTHANDLER_NOTIFICATIONAccount-Status-Notification type='%s' userdn='%s' id=%d msg='%s'ServerMessages.NOTE_EXPORT_FINAL_STATUSExported %d entries and skipped %d in %d seconds (average rate %.1f/sec)ServerMessages.NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_ENDFinished total update: exported domain "%s" from this directory server DS(%s) to remote directory server DS(%s). %sServerMessages.NOTE_FULL_UPDATE_ENGAGED_FOR_REMOTE_STARTStarting total update: exporting %d entries in domain "%s" from this directory server DS(%s) to remote directory server DS(%s)ServerMessages.NOTE_FULL_UPDATE_ENGAGED_FROM_REMOTE_ENDFinished total update: imported domain "%s" from remote directory server DS(%s) to this directory server DS(%s). %sServerMessages.NOTE_IMPORT_PROGRESS_REPORTProcessed %d entries, skipped %d and rejected %d (recent rate %.1f/sec)ServerMessages.NOTE_JVM_HOSTJVM Host: %s, running %s, %d bytes physical memory size, number of processors available %dServerMessages.NOTE_LOAD_BALANCE_REPLICATION_SERVERDirectory Server DS(%s) is disconnecting from replication server RS(%s) at %s for domain "%s" in order to find another replication server in the topology and distribute load more equallyServerMessages.NOTE_REBUILD_PROGRESS_REPORT%.1f%% Completed. Processed %d/%d entries. (recent rate %.1f/sec)ServerMessages.NOTE_RS_HAS_DIFFERENT_GENERATION_ID_THAN_DSRS(%s) generation Id %s does not match DS(%s) generation Id %s, but at least another RS doesServerMessages.NOTE_RS_HAS_DIFFERENT_GROUP_ID_THAN_DSRS(%s) groupId '%s' does not match DS(%s) groupId '%s', but at least one other RS doesServerMessages.NOTE_RS_LATER_THAN_ANOTHER_RS_MORE_UP_TO_DATE_THAN_LOCAL_DSRS(%s) newest change %s is behind another RS which is ahead of DS(%s) newest change %sServerMessages.NOTE_RS_LATER_THAN_LOCAL_DSRS(%s) newest change %s is behind DS(%s) newest change %s, but at least another RS is at the same point or ahead of the DSServerMessages.NOTE_SENT_ALERT_NOTIFICATIONThe Directory Server has sent an alert notification generated by class %s (alert type %s, alert ID %s): %sServerMessages.NOTE_UNRESOLVED_CONFLICT_DELETE_CHILDRENAn unresolved conflict was detected in CSN %s replaying a DELETE of "%s" as child entries exist (renaming child "%s" to "%s"). Consider restoring the parent entry, or deleting the renamed child entriesServerMessages.NOTE_UNRESOLVED_CONFLICT_RENAME_EXISTSAn unresolved conflict was detected in CSN %s replaying a MODIFYDN of "%s" to "%s" which already exists (renaming as "%s"). Consider merging the two entries manually, or deleting one of themServerMessages.NOTE_VERIFY_CLEAN_FINAL_STATUSChecked %d records and found %d error(s) in %d seconds (average rate %.1f/sec)ServerMessages.NOTE_VERIFY_FINAL_STATUSChecked %d entries and found %d error(s) in %d seconds (average rate %.1f/sec)ServerMessages.NOTE_VERIFY_PROGRESS_REPORTProcessed %d out of %d records and found %d error(s) (recent rate %.1f/sec)ServerMessages.WARN_ACI_HOSTNAME_DOESNT_MATCH_CANONICAL_VALUEThe provided Access Control Instruction (ACI) bind rule dns expression value "%s" references hostname %s, which resolves to IP address %s, but the canonical hostname for that IP address is %s. This likely means that the provided hostname will never match any clientsServerMessages.WARN_CONFIG_CHANGE_RESULT_ACTION_REQUIRED%s.%s indicated that administrative action is required for entry %s: messages="%s"ServerMessages.WARN_DEPRECATED_PROPERTYProperty '%s' in %s '%s' is DEPRECATED for removal since %s. Its usage is highly discouragedServerMessages.WARN_DISK_SPACE_FULL_THRESHOLD_CROSSEDDisk free space of %d bytes for directory %s is now below disk low threshold of %d bytes. Backend %s is now offline and will no longer accept any operations until sufficient disk space is restoredServerMessages.WARN_DISK_SPACE_LOW_THRESHOLD_CROSSEDDisk free space of %d bytes for directory %s is now below low threshold of %d bytes. Backend %s is now locked down and will no longer accept any operations from clients until sufficient disk space is restoredServerMessages.WARN_EXCEPTION_STARTING_SESSION_PHASEDirectory server DS(%s) encountered a transient problem while connecting to replication server %s for domain "%s". Directory server will try to connect to a replication server again. The problem was: %sServerMessages.WARN_HEARTBEAT_FAILUREDirectory server DS(%s) is closing its connection to replication server RS(%s) at %s for domain "%s" because it could not detect a heart beatServerMessages.WARN_LDIF_DUPLICATE_ATTREntry %s read from LDIF starting at line %d includes a duplicate attribute %s with value %s. The second occurrence of that attribute value has been skippedServerMessages.WARN_LEGACY_PROPERTYProperty '%s' in %s '%s' is LEGACY since %s. Its usage is highly discouragedServerMessages.WARN_MULTIPLE_KEY_MANAGER_CREATEDFile based key manager provider '%s' has loaded multiple key manager from keystore file '%s'. Only one will be used for securing TLS connections which rely on this key manager provider. Security providers available in the running JVM are %s. The security provider used for loading key manager will be the first in the list which is compatible with the algorithm '%s'ServerMessages.WARN_MULTIPLE_TRUST_MANAGER_CREATEDFile based trust manager provider '%s' has loaded multiple trust manager from truststore file '%s'. Only one will be used for securing TLS connections which rely on this trust manager provider. Security providers available in the running JVM are %s. The security provider used for loading trust manager will be the first in the list which is compatible with the algorithm '%s'ServerMessages.WARN_PEER_REPLICA_IS_TOO_LATEPeer replica '%s' is too late compared to changelog '%s' for domain '%s'. It asked for changes that are not present in the changelog or have been purged. The peer replica will no longer receive replicated changes and must be re-initialized. Diagnostic information follows: %sServerMessages.WARN_PROXY_WILL_IGNORE_SERVERSThe proxy backend '%s' will ignore the discovered servers '%s' from shard '%s' because they do not expose the required base DNs '%s'ServerMessages.WARN_REPLICATION_SERVER_PROPERLY_DISCONNECTEDReplication server RS(%s) at %s has closed the connection to this directory server DS(%s). This directory server will now try to connect to another replication server in order to receive changes for the domain "%s"ServerMessages.WARN_TIMEOUT_WHEN_CROSS_CONNECTIONTimed out while trying to acquire the domain lock for domain "%s". The connection attempt from replication server RS(%s) at %s to this replication server RS(%s) will be aborted. This is probably benign and a result of a simultaneous cross connection attempt -
Uses of LocalizableMessageDescriptor.Arg4 in org.opends.server.extensions
Methods in org.opends.server.extensions with parameters of type LocalizableMessageDescriptor.Arg4Modifier and TypeMethodDescriptionstatic voidIndexedAttributesChecks.checkAllAttributesAreIndexedForExtensibleMatchingRule(Dn cfgDn, Set<Dn> cfgBaseDNs, Collection<AttributeType> attrTypes, MatchingRule matchingRule, LocalizableMessageDescriptor.Arg4<Object, Object, Object, Object> notIndexedMsg, ConfigChangeResult ccr, BackendConfigManager backendConfigManager) Checks whether all attribute types are indexed for a given matching rule.