21 Dec, 2007
3 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3601 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
-
precommit target to the testall target of the build.xml. This allows to reduce the duration of the precommit target by several minutes. Those tests are still run as part of the nightly build or when using the testall target. git-svn-id: https://svn.forgerock.org/opendj/trunk@3599 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
10 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3594 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3593 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
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 -
…s 100% of the time on my machine and prevents the unit tests from completing. See https://opends.dev.java.net/issues/show_bug.cgi?id=2770 git-svn-id: https://svn.forgerock.org/opendj/trunk@3590 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…See issue https://opends.dev.java.net/issues/show_bug.cgi?id=2771 git-svn-id: https://svn.forgerock.org/opendj/trunk@3589 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…e on my machine and prevents the unit tests from completing. See https://opends.dev.java.net/issues/show_bug.cgi?id=2770 git-svn-id: https://svn.forgerock.org/opendj/trunk@3588 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…oes very slow): perform an in-core restart of the server in order to clean up the configuration back-end before running the test cases (in case there are any artifacts left over from previous tests which could slow this one down even more). git-svn-id: https://svn.forgerock.org/opendj/trunk@3587 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
6 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
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3583 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
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3581 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3580 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3579 41b1ffd8-f28e-4786-ab96-9950f0a78031
17 Dec, 2007
17 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3578 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…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@3576 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@3571 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3570 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3569 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3568 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3567 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3566 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3565 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3564 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3563 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3562 41b1ffd8-f28e-4786-ab96-9950f0a78031