04 Jan, 2008
3 commits
-
Update the UserData object properly telling that it is a reversion. git-svn-id: https://svn.forgerock.org/opendj/trunk@3625 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3624 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Close the OutputStream after writing on it as described in the issue report. git-svn-id: https://svn.forgerock.org/opendj/trunk@3623 41b1ffd8-f28e-4786-ab96-9950f0a78031
03 Jan, 2008
8 commits
-
The fix consists of checking whether the specified administrator exists or not before creating it (this is done even in the case where no server had been registered). In addition to that a bug in the way the server registry comparison is made has been fixed. Before these changes when we tried to enable a suffix between two servers that were already replicated, dsreplication enable failed. git-svn-id: https://svn.forgerock.org/opendj/trunk@3622 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Improve the indentation of the resulting set-java-home file generated by dsjavaproperties. Do not use JAVA_ARGS in lib/set-java-properties. Make the setup not to overwrite the environment variables by default. git-svn-id: https://svn.forgerock.org/opendj/trunk@3621 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3620 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…anging the log file permissions to an invalid value. The listeners will now reject changes that will prevent OpenDS from writing to the log files. Fix for issue 2107 git-svn-id: https://svn.forgerock.org/opendj/trunk@3619 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
When a delete is done on the new name of an entry immediately after renaming it, the dependencies between these 2 operations are not detected and the delete can therefore be replayed without waiting for the moddn to complete. This cause the delete to fail and not being replayed. These changes fix the dependency code and add a unit test case allowing to reproduce the problem. git-svn-id: https://svn.forgerock.org/opendj/trunk@3617 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
When a ReplicationBroker disconnect and reconnect quickly to a Replication Server the reconnection sometimes fails. These Changes : - add a unit tests for these condition - fixes race conditions in the Replication Server code to make this test successful git-svn-id: https://svn.forgerock.org/opendj/trunk@3616 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… environment java argument properties. Include a default java.properties file that includes some information about setting the different java properties. git-svn-id: https://svn.forgerock.org/opendj/trunk@3615 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
https://opends.dev.java.net/issues/show_bug.cgi?id=2345 Feature description: ** Before these changes, the monitoring information for the replication contain the information for the replication server itself, and for the LDAP server that are currently connected to it, not for the LDAP servers connected to other RS. ** With these changes, each RS exposes the delay informations for all RSes in the topology. In addition the delay for each server is consolidated across the whole topology. see details in https://www.opends.org/wiki//page/MonitoringReplication Note: - This feature is loosely tested by unit tests. We should probably add more tests in the future but I think it is a good idea to commit the feature and basic tests right now. - The UI part of this feature still need some adaptations to the changes done in the server. git-svn-id: https://svn.forgerock.org/opendj/trunk@3614 41b1ffd8-f28e-4786-ab96-9950f0a78031
02 Jan, 2008
1 commit
-
…ion is printed along with its stack trace. git-svn-id: https://svn.forgerock.org/opendj/trunk@3613 41b1ffd8-f28e-4786-ab96-9950f0a78031
31 Dec, 2007
1 commit
-
…g and provide a better/fair concurrency overall. git-svn-id: https://svn.forgerock.org/opendj/trunk@3611 41b1ffd8-f28e-4786-ab96-9950f0a78031
22 Dec, 2007
2 commits
-
… they are usable from within WebStart installation. git-svn-id: https://svn.forgerock.org/opendj/trunk@3610 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3609 41b1ffd8-f28e-4786-ab96-9950f0a78031
21 Dec, 2007
4 commits
-
The fixes are just cosmetic. They consist basically of: * Add verbosity options for the uninstall and upgrade utilities and make them behave as the verbosity options of the setup. * Make the output of the upgrader consistent with the output of setup and uninstall. * Update the non verbose output of the import LDIF and the import automatically generated data so that a point is displayed every 3 seconds during the import is ongoing. This way the user will not have the impression that the setup is blocked and we show that some work is going on. git-svn-id: https://svn.forgerock.org/opendj/trunk@3607 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…sistent with the other command-lines. git-svn-id: https://svn.forgerock.org/opendj/trunk@3606 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… other command-line utilities. git-svn-id: https://svn.forgerock.org/opendj/trunk@3604 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- Fix return code for add operation on a non existing backend (32 instead of -1 currently) git-svn-id: https://svn.forgerock.org/opendj/trunk@3600 41b1ffd8-f28e-4786-ab96-9950f0a78031
20 Dec, 2007
4 commits
-
…assures no deadlocks will occur between multiple adds and mods. Disabled lock timeouts for add and mod operations since deadlocks can not occur. This prevents txn aborts and op retry expiration due to lock timeouts of add and mod operations when the server is under high write load. Fix for issue 2186 git-svn-id: https://svn.forgerock.org/opendj/trunk@3598 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
hanging tests and failing tests. These changes roll them back until we fully understand the problem. They also enable back the tests that were disabled. git-svn-id: https://svn.forgerock.org/opendj/trunk@3597 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
bugfixes/improvements for the DSML gateway. Here is the detail file by file: . DSMLAbandonOperation -> error handling : abandon Id is now mapped to an unwilling to perform error (was IOException) . DSMLDeleteOperation -> added matchedDN in response (was missing) . DSMLServlet -> added schema validation during JAXB parsing -> dropped usage of an internal JAXB class (useless and risky as this class was renamed in Java 6) -> removed doGet method (useless/cleanup) -> check that if authorization is tagged in http request (bindDN, passwd) are both provided and valid -> better error handling : safer processing with appropriate error messages instead of global try/catch with generic message - in case of parsing error, the request in reparsed with SAX instead of JAXB in order to extract requestID and build appropriate response - in case of processing exception, a mapping (hard-coded) is performed and set in the error response message -> fixed processing onError: default behaviour was to stop once a request failed but the specification defines to continue . DSMLSearchOperation -> added missing filters : "and", "or", "not", "substrings", "greaterOrEqual", "lessOrEqual", "approxMatch", "extensibleMatch" ("equalityMatch" and "present" were provided) -> fixed ability to return attribute names only (typesOnly) . build.xml -> added schema in DSML war file to enable JAXB schema validation git-svn-id: https://svn.forgerock.org/opendj/trunk@3596 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
git-svn-id: https://svn.forgerock.org/opendj/trunk@3595 41b1ffd8-f28e-4786-ab96-9950f0a78031
19 Dec, 2007
4 commits
-
Override the CLI naming argument for virtual attributes so that it is now "name". git-svn-id: https://svn.forgerock.org/opendj/trunk@3592 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
It is now possible to override the default naming argument for dsconfig sub-commands using the CLI profile in the XML definitions. To do this add the "naming-argument-override" attribute to a relation's CLI profile relation element. For example: <adm:relation name="virtual-attribute"> <adm:one-to-many /> <adm:profile name="ldap"> <ldap:rdn-sequence> cn=Virtual Attributes,cn=config </ldap:rdn-sequence> </adm:profile> <adm:profile name="cli"> <cli:relation naming-argument-override="name"> <cli:default-property name="enabled" /> <cli:default-property name="attribute-type" /> </cli:relation> </adm:profile> </adm:relation> git-svn-id: https://svn.forgerock.org/opendj/trunk@3591 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
…a new Local DB Backend is created. The default indexes are aci (presence), objectClass (equality), entryUUID (equality). git-svn-id: https://svn.forgerock.org/opendj/trunk@3586 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Add support to the admin framework for specifying one or more "default" managed objects which should be created automatically when a parent managed object is created. The XML mark-up is provided as part of the parent managed object's relation definition as follows (the sample is taken from the LocalDBBackend XML definition): <adm:relation name="local-db-index"> <adm:one-to-many naming-property="attribute"> <adm:default-managed-object name="aci"> <adm:property name="index-type"> <adm:value>presence</adm:value> </adm:property> <adm:property name="attribute"> <adm:value>aci</adm:value> </adm:property> </adm:default-managed-object> <adm:default-managed-object name="entryUUID"> <adm:property name="index-type"> <adm:value>equality</adm:value> </adm:property> <adm:property name="attribute"> <adm:value>entryUUID</adm:value> </adm:property> </adm:default-managed-object> <adm:default-managed-object name="objectClass"> <adm:property name="index-type"> <adm:value>equality</adm:value> </adm:property> <adm:property name="attribute"> <adm:value>objectClass</adm:value> </adm:property> </adm:default-managed-object> </adm:one-to-many> The functionality is implemented on the client-side API in a generic manner so that it is independent of the underlying driver implementation (so the default indexes would be created if we had an offline direct to file driver as well). git-svn-id: https://svn.forgerock.org/opendj/trunk@3585 41b1ffd8-f28e-4786-ab96-9950f0a78031
18 Dec, 2007
2 commits
-
We now log (notice, instead of error) a more explicit message that tells an SSL connection attempt failed (from node xxx) to the replication server. git-svn-id: https://svn.forgerock.org/opendj/trunk@3584 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The fix consists on adding a verbose option to the setup command-line. With these modifications the graphical setup and the CLI setup (by default) run in non-verbose mode. The logs for import and start are not displayed, nor we make any reference to the ADS when configuring replication. git-svn-id: https://svn.forgerock.org/opendj/trunk@3582 41b1ffd8-f28e-4786-ab96-9950f0a78031
17 Dec, 2007
6 commits
-
…les. The bug prevented the Java WebStart installer to create set-java-home. git-svn-id: https://svn.forgerock.org/opendj/trunk@3577 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3575 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
We check now if it's an absolute path. If it's a relative path, we add the instance root path to get the actual file location git-svn-id: https://svn.forgerock.org/opendj/trunk@3574 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Update the indentation as proposed in the issue description. git-svn-id: https://svn.forgerock.org/opendj/trunk@3573 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Note: this issue is not fully covered by the proposed modifications but all that is missing in order to fix it is to figure out which are the default memory values that we want to propose in the setup. 2620: Server should be started as server JRE and clients should be started as client JREs The proposed solution goes beyond fixing the two issues and proposes a manner for the user to set specific java arguments (and use a specific JVM) for every command-line. Today the user can specify the JVM to be used using the OPENDS_JAVA_HOME environment variable and the java arguments by using the OPENDS_JAVA_ARGS environment variable. In the case of the JVM this covers most of the use cases (in general we will use the same JVM for all the command-lines). However this is quite limiting in the case of the java arguments we pass. For instance in general we want to run the server (start-ds command-line) using the server mode of the JVM but other command-lines using the -client mode of the JVM. In the same manner we might want to have a bigger heap when running the server than when we are running a "lightweight" utility as dsconfig. The proposed solution is to have a properties file called java.properties where the user specifies the different JVM and java arguments to be used for every command-line. Once the user has edited this properties file, (s)he must run a command-line called dsjavaproperties that will update all the scripts to use the arguments specified in that properties file. NOTE: there are a number of command-lines (import-ldif, export-ldif, backup, restore) where the user will be able to specify different java arguments (and different JVM) to use depending on whether the command-line is run in online or offline modes. You can see the comments on java.properties to get more information about this and in general about the different properties that can be set. The modification in the setup basically try to check if the JVM that is being used to run the setup (the one that will be used by default) supports the -client and -server options. Depending on the results of these checks the setup will update the java.properties file and then run dsjavaproperties to update the scripts. git-svn-id: https://svn.forgerock.org/opendj/trunk@3572 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3562 41b1ffd8-f28e-4786-ab96-9950f0a78031
14 Dec, 2007
3 commits
-
- Fix for #795: Changelog fail over unit tests git-svn-id: https://svn.forgerock.org/opendj/trunk@3561 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3560 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Before creating the ldapURL, check if we have an IPv6 address git-svn-id: https://svn.forgerock.org/opendj/trunk@3557 41b1ffd8-f28e-4786-ab96-9950f0a78031
13 Dec, 2007
2 commits
-
In the error messages quote the values that are causing problems to help the user identify proble ms with trailing spaces. git-svn-id: https://svn.forgerock.org/opendj/trunk@3556 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Initialization of the ADS fails when both servers where configured for replication separately. The problem is that the entry that we read from the ADS is not complete (is missing the public key attribute). So when we use the server entry we read from one ADS to register that server in the other ADS the registration is not complete. The fix consists simply on reading the public key certificate in the ADS when we construct the object representing the server. git-svn-id: https://svn.forgerock.org/opendj/trunk@3555 41b1ffd8-f28e-4786-ab96-9950f0a78031