15 Jun, 2007
3 commits
-
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 -
build candidate. git-svn-id: https://svn.forgerock.org/opendj/trunk@2108 41b1ffd8-f28e-4786-ab96-9950f0a78031
14 Jun, 2007
14 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
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2104 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@2102 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@2098 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Re-enable JMX unit-tests (disabled in rev 2071 due to unit-test failure) git-svn-id: https://svn.forgerock.org/opendj/trunk@2097 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
7 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@2092 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
I am commenting out this test case until I can find and restore the ldif file. git-svn-id: https://svn.forgerock.org/opendj/trunk@2091 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
I am commenting out this test case until I can find and restore the ldif file. git-svn-id: https://svn.forgerock.org/opendj/trunk@2090 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
10 commits
-
Changes since 3.2.21 Log File On-Disk Format Changes: None. New Features: None. General Environment Changes 1. Fixed a bug that causes a memory leak for applications when many Environment objects are opened and closed and the CurrentTransaction or TransactionRunner class is used. The problem was reported in this JE Forum thread [#15444] 2. Fixed a bug that prevents correct recovery of data records when duplicates are configured (DatabaseConfig.setSortedDuplicates(true)) for a deferred-write database (DatabaseConfig.setDeferredWrite(true)). When a crash occurs and duplicate data records are recovered that were flushed after the last checkpoint, the wrong key is used for those records. This bug does not occur when the environment is closed normally or a checkpoint is performed after writing data records. [#15474] 3. Fixed a bug that prevents Database.preload from working when duplicates are configured (DatabaseConfig.setSortedDuplicates(true)) for the database. When the preload method was called for a database for which duplicate records exist, an assertion would fire or a NullPointerException would be thrown, depending on whether assertions are enabled. [#15475] 4. Enhanced SerialBinding and the Direct Persistence Layer to use the current thread's context class loader when loading application classes. This allows the JE jar file to be deployed in application servers and other containers as a shared library rather than as an application jar. [#15447] 5. Fixed a bug that caused JE to incorrectly behave as if the cache was very full. The symptoms of this bug are: * Because the problem is a cumulative accounting error, symptoms appear after running for a long period of time. * JE slows down or methods fail to return. Thread dumps show that the com.sleepycat.je.evictor.Evictor class is active and looping. * Dumping EnvironmentStats shows that the adminBytes size (EnvironmentStats.getAdminBytes()) is unreasonably large and may be larger than the maximum cache size or the heap size. * The problem occurs more frequently when blocks of sequential records are deleted. [#15505] 6. Fixed a bug where the cache usage accounting could become inaccurate if the cache size was changed while the application is active (using Environment.setMutableConfig()) and there are outstanding record locks. [#15505] 7. Fixed a bug that caused incorrect query results, and possibly errors during recovery, when a custom duplicate comparison method is configured and that method does not compare all bytes of its operands. A custom comparator should always compare all bytes of its operands and should return non-zero if they are unequal. When updating existing records, JE will detect this kind of incorrect comparator in order to prevent database inconsistency. The problem was reported in this JE Forum thread. [#15527] Direct Persistence Layer (DPL) None. API Changes: 1. Added the EnvironmentStats.getAdminBytes() and getLockBytes() methods, which return the amount of cache used for transactions, administrative structures such as log cleaning metadata, and locks. These values are a subset of the value returned by Environment.getCacheDataBytes() and can provide more insight into how the cache is allocated between actual data and other objects. [#15505] 2. Added the EnvironmentStats.getTotalLogSize method. This new method returns the approximate total size of the JE log files in bytes. It could be used, for example, to detect that the log has exceeded an application disk space limit. [#15480] Utility Changes: None. Configuration, Documentation, Test and Build Changes: None. git-svn-id: https://svn.forgerock.org/opendj/trunk@2086 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
git-svn-id: https://svn.forgerock.org/opendj/trunk@2085 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2084 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2083 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2082 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2081 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2080 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2079 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2078 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2077 41b1ffd8-f28e-4786-ab96-9950f0a78031
11 Jun, 2007
6 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 -
quicksetup one) git-svn-id: https://svn.forgerock.org/opendj/trunk@2072 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2071 41b1ffd8-f28e-4786-ab96-9950f0a78031