30 Jan, 2007
1 commit
-
add schema file task. git-svn-id: https://svn.forgerock.org/opendj/trunk@1058 41b1ffd8-f28e-4786-ab96-9950f0a78031
29 Jan, 2007
4 commits
-
NameFormSyntax class. OpenDS Issue Number: 1169 git-svn-id: https://svn.forgerock.org/opendj/trunk@1057 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The synchronization server is flushing all the queues of the messages received from a LDAP server each time a server needs to retrieve some changes that are not in memory anymore. This cause the reading process of old changes very slow when there is also new changes coming in. The servers that are already late can therefore become more and more late. The solution is to detect the conditions when a flush is necessary by comparing the date of the changeNumber where we want to start with the date of the first ChangeNumber and only flush in those cases. - Also fix some warning at compilation time and when using java 6 - Also fix an problem between test ConfigurableComponentTestCase and the ChangelogTest because ConfigurableComponentTestCase expect all component to be configurable while the dynamic configuration code for the Changelog is not yet implemented. - 2 new unit tests are also included : . scalability test of a synchronization server when one LDAP server is used as a master and several other LDAP servers are used as read only servers : org.opends.server.synchronization.changelog.ChangelogTest.OneWriterMultipleReader() . scalability test of a sycnhronization server when several LDAP Servers are used as master simultaneously : org.opends.server.synchronization.changelog.ChangelogTest.MultipleWriterMultipleReader() These tests do not instantiate the LDAP servers but simulate them by using directly the ChangelogBroker API. The second is failing (issue 1162) and is therefore disabled. git-svn-id: https://svn.forgerock.org/opendj/trunk@1056 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
addition to the Subversion repository have the "svn:eol-style" property set to "native". git-svn-id: https://svn.forgerock.org/opendj/trunk@1055 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This does not allow to cover the code that deals with changelog server to changelog server communications. In order to have more than one changelog services running in the same instance and instance layout, the serverID has been added to the changelogstate dbName. Changelog db path is now configurable, The 2 following tests have been implemented: + /** + * Chaining tests of the changelog code with 2 changelog servers involved + * 2 tests are done here (itest=0 or itest=1) + * + * Test 1 + * - Create changelog server 1 + * - Create changelog server 2 connected with changelog server 1 + * - Create and connect client 1 to changelog server 1 + * - Create and connect client 2 to changelog server 2 + * - Make client1 publish changes + * - Check that client 2 receives the changes published by client 1 + * + * Test 2 + * - Create changelog server 1 + * - Create and connect client1 to changelog server 1 + * - Make client1 publish changes + * - Create changelog server 2 connected with changelog server 1 + * - Create and connect client 2 to changelog server 2 + * - Check that client 2 receives the changes published by client 1 + * + */ git-svn-id: https://svn.forgerock.org/opendj/trunk@1054 41b1ffd8-f28e-4786-ab96-9950f0a78031
28 Jan, 2007
5 commits
-
2007 in their copyright notices. git-svn-id: https://svn.forgerock.org/opendj/trunk@1051 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
set correctly. git-svn-id: https://svn.forgerock.org/opendj/trunk@1050 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1049 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
reduce the time required for it to run during subsequent builds. git-svn-id: https://svn.forgerock.org/opendj/trunk@1048 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
interact with the Subversion workspace. This includes three components: - A new Ant task that stores the current workspace revision number in an Ant property which gets built into DynamicConstants.java and exposed in the --fullversion and "cn=version,cn=monitor" information. - A new Ant task that checks all files that have been locally modified in the current workspace for potential cases in which a copyright date needs to be updated to include the current year. - A change to the coveragediff tool so that it uses the SVNKit library to obtain the diff rather than trying to execute the external svn/svn.exe command. git-svn-id: https://svn.forgerock.org/opendj/trunk@1047 41b1ffd8-f28e-4786-ab96-9950f0a78031
26 Jan, 2007
4 commits
-
…rd to easily point to the latest report git-svn-id: https://svn.forgerock.org/opendj/trunk@1046 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1045 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
processing in OpenDS. git-svn-id: https://svn.forgerock.org/opendj/trunk@1044 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
getting attributes, comparing filters, etc.) work properly with attribute subtypes. Additional work is required in the JE backend to fully support this capability, particularly in the area of index management for modify and modify DN operations. OpenDS Issue Number: 739 git-svn-id: https://svn.forgerock.org/opendj/trunk@1043 41b1ffd8-f28e-4786-ab96-9950f0a78031
25 Jan, 2007
4 commits
-
and matching rule OIDs used in various test cases. git-svn-id: https://svn.forgerock.org/opendj/trunk@1042 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ty test suites. Also, made multiple tests with in test case into simply multiple operations, and made a preamble and postamle steps. git-svn-id: https://svn.forgerock.org/opendj/trunk@1041 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1039 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
umbrella of issue #1163. The individual issues addressed include: * 1139 -- Properly handle OBSOLETE flag in schema elements. The OBSOLETE flag is now recognized when processing matching rules, attribute types, object classes, name forms, DIT content rules, DIT structure rules, and matching rule uses. It essentially provides a way to "deprecate" a schema element so that existing data that makes use of them will still be treated properly, but the server will not allow newly-created elements to reference them. * 1145 -- Consider updating X-ORIGIN to reference newer RFCs. When the schema configuration files were originally written, there were a number of references to RFC 2252 and RFC 2256 that were updated in RFC 4512 and RFC 4519, among others. The X-ORIGIN extension for each element in the 00-core.ldif schema configuration file should now reference the latest specification that contains that element. * 1146 -- Consider enforcing object class inheritance restrictions. The server will now ensure that abstract classes can only inherit from other abstract classes, that auxiliary classes can only inherit from abstract classes and other auxiliary classes, and that structural classes can only inherit from abstract classes and other structural classes. Further, all structural object classes must include the "top" abstract class as the root of their inheritance chain. * 1147 -- Consider enforcing attribute type inheritance restrictions. The server will now ensure that a subordinate attribute type will have the same usage as its superior type. Further, the server will enforce that a subordinate attribute type may be collective if and only if its superior type is collective. Due to the subjective nature of the "refinement" clause for syntax inheritance, no check will be made regarding the syntax relationship between a superior and subordinate attribute type. * 1151 -- DIT content rule validation isn't handled correctly. The server will now allow attribute types to appear in an entry if they are included in the required or optional attribute type lists for a DIT content rule even if those attributes are not allowed by any of the entry's associated object classes. Further, the DIT content rule validation process will now ensure that none of the prohibited attribute types are required by the structural object class or any of the allowed auxiliary object classes. * 1158 -- Attribute syntaxes describing schema elements aren't strict enough. Previously, in most cases that one schema element referenced another element that was not defined (e.g., an object class allows an attribute type that is not defined in the server schema), the server would ignore the unresolved dependency. The server will now fail to validate schema elements that depend on other schema elements which are not defined in the server schema. Similarly, there were cases in which the server did not properly validate that an object class was of the appropriate type (e.g., for a DIT content rule, there was no check to ensure that the structural object class was actually declared structural, or that all of the allowed auxiliary objectclasses were actually declared auxiliary). The server will also fail to validate schema elements with these kinds of problems. * 1159 -- Incomplete attribute type usage constraints. The server did not properly ensure that COLLECTIVE attribute types had a usage of userApplications, and that NO-USER-MODIFICATION attribute types had an operational usage. * 1164 -- Need more complete DIT structure rule validation. The server did not properly ensure that if an entry's parent was associated with a DIT structure rule, that entry would only be valid if it was covered by a DIT structure rule which listed the parent's DIT structure rule as a superior rule. * 1165 -- Consider reduced name form and DIT structure rule checking. The server would often perform more schema validation than necessary for most types of operations. In particular, name form and DIT structure rule validation should not be required for modify operations, and DIT structure rule validation should also not be required for LDIF import operations since we cannot guarantee that the parent will be accessible. git-svn-id: https://svn.forgerock.org/opendj/trunk@1036 41b1ffd8-f28e-4786-ab96-9950f0a78031
24 Jan, 2007
1 commit
-
When doing scalability tests I've noticed that some of the code inside the SynchronizationDomain.pendingChanges lock is not usefull. I've therefore moved it outside of the lock. There are no tests for this because this is only a small perf improvement. git-svn-id: https://svn.forgerock.org/opendj/trunk@1033 41b1ffd8-f28e-4786-ab96-9950f0a78031
23 Jan, 2007
7 commits
-
test cases. They didn't provide much additional value beyond that which was already available from smaller values, and removing them can notably improve the time required to run those tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@1023 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1020 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1019 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ject-unauthenticated-requests". git-svn-id: https://svn.forgerock.org/opendj/trunk@1018 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…thenticated-requests". git-svn-id: https://svn.forgerock.org/opendj/trunk@1017 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1016 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
before returning. git-svn-id: https://svn.forgerock.org/opendj/trunk@1010 41b1ffd8-f28e-4786-ab96-9950f0a78031
22 Jan, 2007
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1009 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
was not waiting for the reader thread to complete it's job before returning the number of message read thus causing the test to fail git-svn-id: https://svn.forgerock.org/opendj/trunk@1007 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
1. Wrapped TestNG suite runner with our own (SuiteRunner.java). When there is an uncaught exception in the tests, this gives us the stack trace and forces the tests to exit. This should make it easier to track down OutOfMemoryErrors in the future. 2. Added our own listener for the tests. This does the following * As soon as a test fails, it prints it out all of the info to the screen. Test method, error message, stacktrace, parameters * At the end of the tests, it summarizes all of the tests that failed. * It generates a new test report in text format. The html report generator was a real memory hog. 3. Changes to build.xml * Test output is suppressed by default. * The coverage report is generated even if the tests failed. * Exposed the ability to rerun only the failed tests with -Dtest.failed=true. * The 'runtests' target prints out information about additional test options. * Two small fixes so that ant doesn't recompile files that haven't changed. * Removed tabs. This was mostly in the status panel code. * Reverted the -Xmx256M temporary fix for the unit tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@1006 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…an uncaught exception in the tests, this gives us the stack trace and forces the tests to exit. This should make it easier to track down OutOfMemoryErrors in the future. 2. Added our own listener for the tests. This does the following * As soon as a test fails, it prints it out all of the info to the screen. Test method, error message, stacktrace, parameters * At the end of the tests, it summarizes all of the tests that failed. * It generates a new test report in text format. The html report generator was a real memory hog. 3. Changes to build.xml * Test output is suppressed by default. * The coverage report is generated even if the tests failed. * Exposed the ability to rerun only the failed tests with -Dtest.failed=true. * The 'runtests' target prints out information about additional test options. * Two small fixes so that ant doesn't recompile files that haven't changed. * Removed tabs. This was mostly in the status panel code. * Reverted the -Xmx256M temporary fix for the unit tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@1005 41b1ffd8-f28e-4786-ab96-9950f0a78031
19 Jan, 2007
3 commits
-
modifiersName, and modifyTimestamp attributes are included in the subschema subentry as recommended in RFC 4512 section 4.2. The create timestamp will be set to the oldest modification time of all the schema configuration files. The modify timestamp will be initially set to the youngest modification time of all the schema configuration files, but if the schema is updated with the server online then the modifiersName and modifyTimestamp will be updated accordingly. OpenDS Issue Number: 1157 git-svn-id: https://svn.forgerock.org/opendj/trunk@1004 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
with the precommit and all targets. git-svn-id: https://svn.forgerock.org/opendj/trunk@1003 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1002 41b1ffd8-f28e-4786-ab96-9950f0a78031
18 Jan, 2007
5 commits
-
…case fails so it is currently disabled. git-svn-id: https://svn.forgerock.org/opendj/trunk@1000 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…essages attribute as well as writing it to the error log. Enabled test in TasksTestCase to make sure log-messages attribute is not empty when the task fails. Fix for issue 647 git-svn-id: https://svn.forgerock.org/opendj/trunk@999 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… in the zip stream if the backend is empty. On restore, this file will not be restored. Fix for issue 969 git-svn-id: https://svn.forgerock.org/opendj/trunk@998 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- fix the regression (schema problem) - disabled the ChangelogTest.stopChangelog() test that appear to cause some hangs. ---------- This change includes a set of new unit tests dedicated to the startup phase of the synchronization server (former changelog server) and the connection phase of client LDAP server to this synchronization server. These tests cover various cases of this connection checking that the adequate changes are then sent to the client. This change also include the fix for : issue 1155 : synchronization server miss one change when a new LDAP server is added to the topology git-svn-id: https://svn.forgerock.org/opendj/trunk@996 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
used to run the unit tests. Also, re-enable the JMX and search filter test cases that had been disabled. git-svn-id: https://svn.forgerock.org/opendj/trunk@995 41b1ffd8-f28e-4786-ab96-9950f0a78031
17 Jan, 2007
2 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@991 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… when we run our unit tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@990 41b1ffd8-f28e-4786-ab96-9950f0a78031