20 Jun, 2007
7 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2137 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- Extracted common interface DatabaseContainer from DN2ID, ID2Entry, etc... classes. - Moved database read and write methods from EntryContainer to DatabaseContainer. - Added index configuration to the XML based admin framework. - Removed redundant configuration objects (Config, IndexConfig). - Added exclusive/shared lock to EntryContainer. All access to an EntryContainer must acquire a lock before using the internal DatabaseContainers or making configuration changes. - Added the ability to add/remove/modify indexes with the backend online. Server will issue rebuild required warning when adding new indexes or sub-indexes (equality, substring, presence...). - Added the ability to change the index entry limit for both the backend and each index with the backend online. Server will issue rebuild required warning if the previous limit has been exceeded. - Added the ability to change entry compression and index substring length setting while the backend is online. - Added a persistent state database to each EntryContainer to persist backend configuration between server restarts. Server will issue rebuild required warning if a new index is added when the backend is offline. - Added a trusted flag to indexes so that non existent keys will not be interpreted as an empty entry ID set when an index is untrusted. An index is untrusted when it is added to an non-empty EntryContainer or an inconsistency is detected. Server will issue warning on startup to rebuild the index. - Fixed a issue where the LDIF import process stops responding if the temporary import dir is full or unwritable. Fix for issue 1480 1455 1575 git-svn-id: https://svn.forgerock.org/opendj/trunk@2135 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2134 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2133 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
-q, --useStartTLS Use StartTLS to secure communication with the server -X, --trustAll Trust all server SSL certificates -N, --certNickname {nickname} Nickname of certificate for SSL client authentication git-svn-id: https://svn.forgerock.org/opendj/trunk@2132 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
The replication monitoring was showing information for - the replication domains - the remote LDAP servers connected to the replication server - the remote replication server connected to the replication server but does not show any information for a local replication server. A replication server that is started but does not have any server connected yet therefore does not publish any monitoring information. This changes add a new monitoring entry that fixes this lack and also change the names of the monitoring entries of the server connected to the replication server to include the "remote" keyword. As an example, the monitoring information of a server that is also its replication server now looks like this : dn: cn=Replication Server 8989 1,cn=monitor objectClass: extensibleObject objectClass: top objectClass: ds-monitor-entry replication server id: 1 replication server port: 8989 base-dn: dc=example,dc=com cn: Replication Server 8989 1 dn: cn=Replication plugin dc=example\,dc=com,cn=monitor objectClass: extensibleObject objectClass: top objectClass: ds-monitor-entry lost-connections: 0 connected-to: localhost/127.0.0.1:8989 resolved-naming-conflicts: 0 replayed-updates: 0 base-dn: dc=example,dc=com unresolved-naming-conflicts: 0 max-send-window: 100 max-rcv-window: 100 resolved-modify-conflicts: 0 current-send-window: 100 cn: Replication plugin dc=example,dc=com pending-updates: 0 sent-updates: 0 received-updates: 0 current-rcv-window: 100 replayed-updates-ok: 0 dn: cn=Remote LDAP Server dc=example\,dc=com furon 1,cn=monitor objectClass: extensibleObject objectClass: top objectClass: ds-monitor-entry approximate-delay: 0 max-waiting-changes: 10000 update-sent: 0 waiting-changes: 0 update-received: 0 base-dn: dc=example,dc=com update-waiting-acks: 0 max-send-window: 100 ack-received: 0 max-rcv-window: 100 current-send-window: 100 cn: Remote LDAP Server dc=example,dc=com furon 1 server-id: 1 LDAP-Server: furon current-rcv-window: 100 ack-sent: 0 git-svn-id: https://svn.forgerock.org/opendj/trunk@2131 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2130 41b1ffd8-f28e-4786-ab96-9950f0a78031
19 Jun, 2007
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2128 41b1ffd8-f28e-4786-ab96-9950f0a78031
18 Jun, 2007
8 commits
-
…SL configured. The cause of the problem was found to be that files important to SSL configuration (namely the keystore file) were not copied from the old installation to the upgraded installation. This commit copies files that do not appear in the upgraded config directory from the old config directory. git-svn-id: https://svn.forgerock.org/opendj/trunk@2127 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2126 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2124 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…n the default implementation which contains the cause's class name as well (this is the correct behavior because admin client exceptions are supposed to "adapt" underlying impl exceptions, so they should use the adapted exception's message). git-svn-id: https://svn.forgerock.org/opendj/trunk@2123 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Add the following global options in dsservice to handle client keystore Also modify ads.util package for this purpose. -K, --keyStorePath {keyStorePath} Certificate keystore path --keyStorePassword {keyStorePassword} Certificate keystore PIN -u, --keyStorePasswordFile {path} Certificate keystore PIN file git-svn-id: https://svn.forgerock.org/opendj/trunk@2122 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
Also modify ads.util package for this purpose. -K, --keyStorePath {keyStorePath} Certificate keystore path --keyStorePassword {keyStorePassword} Certificate keystore PIN -u, --keyStorePasswordFile {path} Certificate keystore PIN file git-svn-id: https://svn.forgerock.org/opendj/trunk@2121 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
git-svn-id: https://svn.forgerock.org/opendj/trunk@2119 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
A listener thread has received an update message, processed it and during the postOperation phase is now trying to send update that were in the PendingChanges Queue to the Replication Server. However it is blocked because the protocol window is closed. Unfortunately it is still holding the PeningChanges locks and therefore the other listenerthread are blocked and don't read the ack messages that would open the window. The solution is to split the pendingChanges is 2 queues : one for the local update and one for the remote updates so that the receiving threads are not locked anymore because the window is closed. git-svn-id: https://svn.forgerock.org/opendj/trunk@2118 41b1ffd8-f28e-4786-ab96-9950f0a78031
15 Jun, 2007
5 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2116 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…bing for getting the quicksetup tests' workspace server configured enough so that it is startable and stoppable for testing. - Consolidated some duplicated code that was formerly scattered around in various classes into the classes for which we have test cases. - Fixes bug determining outside log and db paths which were previously always assumed to be relative paths (see issue 1798). - Disables Logger output to the console for the 'status' CLI since newly added debug log messages were showing up there. - Fixed a resource not found exception that happened when the uninstaller tried to delete a file that didn't exist. git-svn-id: https://svn.forgerock.org/opendj/trunk@2115 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2111 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This change modifies the admin framework XML schema so that it is possible for all types of required admin action to have a description. For example, when there is no additional administrator action required when a property is modified, it is sometimes nice to indicate how the change will dynamically take effect. In addition, it is now possible to query the specific type of admin action associated with a property and its synopsis via the admin framework APIs. git-svn-id: https://svn.forgerock.org/opendj/trunk@2110 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
-P, --trustStorePath {trustStorePath} Certificate trust store path --trustStorePassword {trustStorePassword} Certificate trust store PIN -U, --TrustStorePasswordFile {path} Certificate trust store PIN file git-svn-id: https://svn.forgerock.org/opendj/trunk@2109 41b1ffd8-f28e-4786-ab96-9950f0a78031
14 Jun, 2007
10 commits
-
case in which there is more than one entry in a schema configuration file (or if there is garbage after the first entry) and log it as a warning message. OpenDS Issue Number: 1795 git-svn-id: https://svn.forgerock.org/opendj/trunk@2107 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2106 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…issing files from previous commit. See issue 1779 for more info. git-svn-id: https://svn.forgerock.org/opendj/trunk@2105 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
and logging proper error message in case of unlikely failures. git-svn-id: https://svn.forgerock.org/opendj/trunk@2103 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2101 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2100 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2099 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2096 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
build due to a number of missing symbols. git-svn-id: https://svn.forgerock.org/opendj/trunk@2095 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…sue 1779 for more info. git-svn-id: https://svn.forgerock.org/opendj/trunk@2094 41b1ffd8-f28e-4786-ab96-9950f0a78031
13 Jun, 2007
4 commits
-
…ged object can be grouped together. Tagging will enable us to automatically generate more user-friendly documentation and administration tools as a result of them being easier to navigate and search. For example, an administration CLI will be able to split the available set of sub-commands into categories, thus making it easier for administrators to find the sub-command that they need. This change is implemented as follows: * provide an extensible way in which tags can be defined: the XML root configuration definition element now supports an "adm:tag-definition" element, which can be used as follows: <adm:tag-definition name="logging"> <adm:synopsis>Logging</adm:synopsis> </adm:tag-definition> * provide a means for tagging managed object definitions with zero or more tags using an "adm:tag" element, which can be used as follows: <adm:tag name="logging"/> * add support to the admin framework APIs for querying a managed object definition's tags * define an initial set of tags and tag managed object definitions appropriately (this is just an initial guess and is likely to change): * logging * replication (incl. mmr) * database (incl. caching) * security (authn and authz) * identity (user account management, pwp, etc) * core (connection handlers, virtual attributes, etc) git-svn-id: https://svn.forgerock.org/opendj/trunk@2093 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
git-svn-id: https://svn.forgerock.org/opendj/trunk@2089 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2088 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2087 41b1ffd8-f28e-4786-ab96-9950f0a78031
12 Jun, 2007
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2084 41b1ffd8-f28e-4786-ab96-9950f0a78031
11 Jun, 2007
4 commits
-
…s not create a quickstart.CliApplication but rather relies on the server package for the installation. I just added an NPE guard. git-svn-id: https://svn.forgerock.org/opendj/trunk@2076 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…perty definitions. The CLI profile defines two annotations at the moment: * the operand name which should be used in sub-command usage help to identify the names of managed objects being added, removed, modified, etc * the list of properties which should be displayed by default in list-xxx sub-commands. For example, when listing connection handlers we can display a summary table that lists the "enabled", "listen-port", and "use-ssl" properties by default Both of these annotations apply only to relation definitions. Existing relations have been updated to include these CLI annotations, although their content is subject to change if we decide that better operand names/default properties exist. These annotations will be used in the forthcoming dsconfig CLI. git-svn-id: https://svn.forgerock.org/opendj/trunk@2075 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2074 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…s which define a pattern constraint. The usage string is used when the syntax of a property needs to be displayed, for example in a CLI help screen or in server-side log messages when a bad property value is encountered. For example, a property whose values must be a valid UNIX mode could have the following string syntax definition: <adm:string> <adm:pattern> <adm:regex>^[0-7][0-7][0-7]$</adm:regex> <adm:usage>MODE</adm:usage> <adm:synopsis> An valid UNIX mode string. The mode string must contain three digits between zero and seven. </adm:synopsis> </adm:pattern> </adm:string> Existing string based properties have been updated with appropriate usage. git-svn-id: https://svn.forgerock.org/opendj/trunk@2073 41b1ffd8-f28e-4786-ab96-9950f0a78031