From b4f8838b15342670c31753a484abf0129e3c9653 Mon Sep 17 00:00:00 2001 From: jcduff <jcduff@localhost> Date: Thu, 23 Oct 2008 14:04:24 +0000 Subject: [PATCH] The commit will bring the following features : - An updated version of the underlying database. BDB JE 3.3 is now used. - Attribute API refactoring providing a better abstraction and offering improved performances. - A new GUI called the Control-Panel to replace the Status-Panel: the specifications for this GUI are available on OpenDS Wiki and contains a link to a mockup. See <https://www.opends.org/wiki/page/ControlPanelUISpecification>. - Some changes in the replication protocol to implement "Assured Replication Mode". The specifications are on OpenDS Wiki at <https://www.opends.org/wiki/page/AssuredMode> and section 7 described some of the replication changes required to support this. Assured Replication is not finished, but the main replication protocol changes to support it are done. As explained by Gilles on an email on the Dev mailing list (http://markmail.org/message/46rgo3meq3vriy4a), with these changes the newer versions of OpenDS may not be able to replicate with OpenDS 1.0 instances. - Support for Service Tags on the platforms where the functionality is available and enabled. Specifications are published at <https://www.opends.org/wiki/page/OpenDSServiceTagEnabled>. For more information on Service Tags see <http://wikis.sun.com/display/ServiceTag/Sun+Service+Tag+FAQ>. - The Admin Connector service. In order to provide agentry of the OpenDS server at any time, a new service has been added, dedicated to the administration, configuration and monitoring of the server. An overview of the Admin Connector service and it's use is available on the OpenDS wiki <https://www.opends.org/wiki/page/ManagingAdministrationTrafficToTheServer> - Updates to the various command line tools to support the Admin Connector service. - Some internal re-architecting of the server to put the foundation of future developments such as virtual directory services. The new NetworkGroups and WorkFlow internal services which have been specified in <https://www.opends.org/wiki/page/BasicOperationRoutingThroughNetworkGroup> are now implemented. - Many bug fixes... --- opendj-sdk/opends/src/messages/messages/replication.properties | 123 +++++++++++++++++++++++++++++++--------- 1 files changed, 95 insertions(+), 28 deletions(-) diff --git a/opendj-sdk/opends/src/messages/messages/replication.properties b/opendj-sdk/opends/src/messages/messages/replication.properties index fce45c0..d405c94 100644 --- a/opendj-sdk/opends/src/messages/messages/replication.properties +++ b/opendj-sdk/opends/src/messages/messages/replication.properties @@ -73,15 +73,15 @@ base dn : %s MILD_ERR_ERROR_SEARCHING_RUV_15=Error %s when searching for server state %s : \ %s base dn : %s -NOTICE_SERVER_DISCONNECT_16=%s has disconnected from this replication server +NOTICE_SERVER_DISCONNECT_16=%s has disconnected from this replication server %s NOTICE_NO_CHANGELOG_SERVER_LISTENING_17=There is no replication server \ listening on %s NOTICE_FOUND_CHANGELOGS_WITH_MY_CHANGES_18=Found %d replication server(s) with \ -up to date changes for suffix %s +up to date changes for suffix %s, in server id %s NOTICE_NEED_MORE_THAN_ONE_CHANGELOG_SERVER_19=More than one replication \ server should be configured -SEVERE_ERR_EXCEPTION_STARTING_SESSION_20=Caught Exception during initial \ - communication on domain %s with replication server %s : %s +SEVERE_ERR_EXCEPTION_SENDING_TOPO_INFO_20=Caught IOException while sending \ + topology info (for update) on domain %s for %s server %s : %s MILD_ERR_CANNOT_RECOVER_CHANGES_21=Error when searching old changes from the \ database for base DN %s NOTICE_COULD_NOT_FIND_CHANGELOG_WITH_MY_CHANGES_22=Could not find a \ @@ -103,8 +103,8 @@ SEVERE_ERR_EXCEPTION_CHANGELOG_TRIM_FLUSH_29=Error during the Replication \ Server database trimming or flush process. The Changelog service is going to \ shutdown -SEVERE_ERR_CHANGELOG_CONNECTION_ERROR_30=Error during Replication server \ - message processing . Connection from %s is rejected +SEVERE_ERR_REPLICATION_SERVER_CONNECTION_ERROR_30=Error in Replication Server \ + handshake processing. Connection from/to %s is aborted SEVERE_ERR_UNKNOWN_MESSAGE_31=%s has sent an unknown message. Closing the \ connection SEVERE_ERR_WRITER_UNEXPECTED_EXCEPTION_32=An unexpected error happened \ @@ -154,10 +154,10 @@ as an IP address NOTICE_READER_NULL_MSG_52=Received a Null Msg from %s NOTICE_READER_EXCEPTION_53=Exception when reading messages from %s -SEVERE_ERR_DUPLICATE_SERVER_ID_54=Servers %s and %s have the same ServerId : \ - %d -SEVERE_ERR_DUPLICATE_REPLICATION_SERVER_ID_55=Replication Servers %s and %s \ - have the same ServerId : %d +SEVERE_ERR_DUPLICATE_SERVER_ID_54=In Replication server %s: servers %s and %s \ +have the same ServerId : %d +SEVERE_ERR_DUPLICATE_REPLICATION_SERVER_ID_55=In Replication server %s: \ +replication servers %s and %s have the same ServerId : %d SEVERE_ERR_BAD_HISTORICAL_56=Entry %s was containing some unknown historical \ information, This may cause some inconsistency for this entry MILD_ERR_CANNOT_ADD_CONFLICT_ATTRIBUTE_57=A conflict was detected but the \ @@ -172,12 +172,10 @@ SEVERE_ERR_REPLICATION_COULD_NOT_CONNECT_61=The Replication is configured for \ suffix %s but was not able to connect to any Replication Server NOTICE_NOW_FOUND_SAME_GENERATION_CHANGELOG_62=Replication is up and running \ - for domain %s with replication server %s - data generation is %s + for domain %s with replication server id %s %s - local server id is %s - data \ + generation is %s NOTICE_DISCONNECTED_FROM_CHANGELOG_63=The connection to Replication Server %s \ - has been dropped by the Replication Server -SEVERE_ERR_CHANGELOG_ERROR_SENDING_INFO_64=An unexpected error occurred \ - while sending a Server Info message to %s. This connection is going to be \ - closed and reopened + %s has been dropped by the Replication Server for %s in local server id %s SEVERE_ERR_CHANGELOG_ERROR_SENDING_ERROR_65=An unexpected error occurred \ while sending an Error Message to %s. This connection is going to be closed \ and reopened @@ -203,15 +201,16 @@ searching in %s for the generation ID : %s SEVERE_ERR_UPDATING_GENERATION_ID_76=An unexpected error %s occurred \ when updating generation ID for the domain : %s -NOTICE_BAD_GENERATION_ID_77=On suffix %s. server %s presented generation ID=%s \ -when expected generation ID=%s. Consequently, replication is degraded for that server -NOTICE_RESET_GENERATION_ID_78=The generation ID has been reset for domain %s.\ -Replication is now degraded for this domain -MILD_ERR_ERROR_MSG_RECEIVED_79=The following error has been received : <%s> -MILD_ERR_IGNORING_UPDATE_FROM_80=Update <%s> received from server <%s> is \ -ignored due to a bad generation ID of this server -MILD_ERR_IGNORING_UPDATE_TO_81=In %s, update <%s> will not be sent to server %s\ - with generation ID=%s different from expected generation ID=%s +NOTICE_BAD_GENERATION_ID_FROM_RS_77=On suffix %s, replication server %s presented \ + generation ID=%s when expected generation ID=%s +NOTICE_RESET_GENERATION_ID_78=The generation ID has been resetted for domain %s. \ + New reference generation id is %s +MILD_ERR_ERROR_MSG_RECEIVED_79=The following error has been received : %s +MILD_ERR_IGNORING_UPDATE_FROM_RS_80=In RS %s for dn %s, update %s received from \ + RS %s is ignored due to a bad generation id of remote RS (local genid: \ + %s, remote genid: %s) +MILD_ERR_IGNORING_UPDATE_TO_RS_81=In RS %s for dn %s, update %s will not be sent \ + to RS %s with generation id %s different from local generation id %s SEVERE_ERR_INIT_IMPORT_NOT_SUPPORTED_82= Initialization cannot be done because \ import is not supported by the backend %s SEVERE_ERR_INIT_EXPORT_NOT_SUPPORTED_83= Initialization cannot be done because \ @@ -240,10 +239,11 @@ the replication server backend SEVERE_ERR_UNKNOWN_DN_95=The base DN %s is not stored by any of the \ Directory Server backend -NOTICE_NOW_FOUND_BAD_GENERATION_CHANGELOG_96=Replication is up but degraded \ - for domain %s with replication server %s - local data generation is %s \ - - replication server data generation is %s - This may be only temporary \ - or require a full resynchronization +NOTICE_NOW_FOUND_BAD_GENERATION_CHANGELOG_96=Replication is connected to \ + replication server, but has a different generation id for domain %s than \ + replication server %s - local data generation is %s - replication server data \ + generation is %s - This may be only temporary or requires a full \ + resynchronization NOTICE_HEARTBEAT_FAILURE_97=%s is closing the session \ because it could not detect a heartbeat SEVERE_ERR_REPLICATONBACKEND_IMPORT_LDIF_NOT_SUPPORTED_98=The replication \ @@ -279,3 +279,70 @@ SEVERE_ERR_RESET_GENERATION_CONN_ERR_ID_118=The generation ID could not be \ reset for domain %s because it is NOT connected to the replication. You should \ check in the configuration that the domain is enabled +SEVERE_ERR_EXCEPTION_STARTING_SESSION_PHASE_119=Caught Exception during initial \ + communication (phase %s) on domain %s with replication server %s : %s +NOTICE_NEW_SERVER_WITH_SAME_GROUP_ID_120=Disconnecting from replication server \ + as a new one with our group id (%s) just arrived in topology. This is for \ + domain %s and we have server id %s +SEVERE_ERR_RS_DN_DOES_NOT_MATCH_121=DN sent by remote replication server: %s does \ + not match local replication server one: %s +SEVERE_ERR_DS_DN_DOES_NOT_MATCH_122=DN sent by replication server: %s does \ + not match local directory server one: %s +SEVERE_ERR_EXCEPTION_FORWARDING_RESET_GEN_ID_123=Caught IOException while \ + forwarding ResetGenerationIdMsg to peer replication servers for domain %s : %s +SEVERE_ERR_DS_INVALID_INIT_STATUS_124=Computed invalid initial status: %s in \ + DS replication domain %s with server id %s +SEVERE_ERR_RS_INVALID_INIT_STATUS_125=Replication server received invalid \ + initial status: %s for replication domain %s from server id %s +SEVERE_ERR_DS_INVALID_REQUESTED_STATUS_126=Received invalid requested status %s \ + in DS replication domain %s with server id %s +SEVERE_ERR_RS_CANNOT_CHANGE_STATUS_127=Could not compute new status in RS \ + replication domain %s for server id %s. Was in %s status and received %s event +SEVERE_ERR_DS_CANNOT_CHANGE_STATUS_128=Could not compute new status in DS \ + replication domain %s with server id %s. Was in %s status and received %s event +SEVERE_ERR_EXCEPTION_CHANGING_STATUS_AFTER_RESET_GEN_ID_129=Caught IOException \ + while changing status for domain %s and serverId: %s after reset for \ + generation id: %s +SEVERE_ERR_RECEIVED_CHANGE_STATUS_NOT_FROM_DS_130=Received change status \ + message does not come from a directory server (dn: %s, server id: %s, msg: %s) +NOTICE_DIRECTORY_SERVER_CHANGED_STATUS_131=Directory server %s for dn %s \ + changed his status to %s +SEVERE_ERR_RS_INVALID_NEW_STATUS_132=Received invalid new status %s \ + in RS for replication domain %s and directory server id %s +SEVERE_WARN_CONNECTED_TO_SERVER_WITH_WRONG_GROUP_ID_133=Connected to a \ + replication server with wrong group id. We have group id %s and replication \ + server id %s %s has group id %s. This is for domain %s in directory server %s +SEVERE_ERR_EXCEPTION_SENDING_CS_134=Replication broker with dn %s and server \ + id %s failed to signal status change because of: %s +MILD_ERR_IGNORING_UPDATE_FROM_DS_BADGENID_135=In RS %s for dn %s, update %s \ + received from DS %s is ignored due to a bad generation id of DS (local genid: \ + %s, remote genid: %s) +MILD_ERR_IGNORING_UPDATE_TO_DS_BADGENID_136=In RS %s for dn %s, update %s will \ + not be sent to DS %s with generation id %s different from local generation id %s +MILD_ERR_IGNORING_UPDATE_FROM_DS_FULLUP_137=In RS %s for dn %s, update %s \ + received from DS %s is ignored due to DS in full update +MILD_ERR_IGNORING_UPDATE_TO_DS_FULLUP_138=In RS %s for dn %s, update %s will \ + not be sent to DS %s in full update +SEVERE_ERR_EXCEPTION_CHANGING_STATUS_FROM_STATUS_ANALYZER_139=Caught \ + IOException while changing status for domain %s and serverId: %s from status \ +analyzer: %s +NOTICE_BAD_GEN_ID_IN_FULL_UPDATE_140=Replication server %s for dn %s: directory \ +server %s must stay in full update although a generation id reset has been \ +ordered (from %s to %s) +NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_START_141=Local directory server %s is \ + starting online full update for importing suffix %s data from remote \ + directory server %s +NOTICE_FULL_UPDATE_ENGAGED_FROM_REMOTE_END_142=Local directory server %s has \ + finished online full update for importing suffix %s data from remote \ + directory server %s +NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_START_143=Local directory server %s is \ + starting online full update for exporting suffix %s data to remote directory \ + server %s +NOTICE_FULL_UPDATE_ENGAGED_FOR_REMOTE_END_144=Local directory server %s has \ + finished online full update for exporting suffix datat %s to remote directory \ + server %s +NOTICE_TIMEOUT_WHEN_CROSS_CONNECTION_145=Timed out trying to acquire the domain \ +lock for %s. Connection attempt from replication server %s to local replication \ +server %s will be aborted. Simultanate cross connection attempt ? +NOTICE_BAD_GENERATION_ID_FROM_DS_146=On suffix %s, directory server %s presented \ + generation ID=%s when expected generation ID=%s -- Gitblit v1.10.0