29 Aug, 2007
12 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2847 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Refactor some code and put it in CliApplicationHelper. Fix some minor bugs in the output of the command-lines. git-svn-id: https://svn.forgerock.org/opendj/trunk@2846 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2845 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2844 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Overview: This change completes the dsconfig interactive mode. dsconfig now supports two levels of interactivity: 1) Usage: dsconfig A top-level menu driven text based console. Using this interactive mode the user is able able to perform multiple administrative tasks via a menu-driven interface 2) Usage: dsconfig <sub-command> dsconfig will perform the administrative task associated with the specified sub-command prompting the user for any missing information required in order to complete the task In addition, both interactive modes will prompt the user for any connection parameters not specified on the command line. Note that it is possible to run dsconfig non-interactively using the "-n" option. Although this is only available when a sub-command is provided. Other changes: 1) part of this work required implementing a generic CLI application framework. This includes an API for building and running menu-based interfaces. The classes are located in a new package called org.opends.server.util.cli 2) the dsconfig related messages have been relocated into a separate dsconfig-specific properties file. git-svn-id: https://svn.forgerock.org/opendj/trunk@2843 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2842 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2841 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… use when this was not provided. Before asking to use SSL or startTLS check that they can actually be used. Rename StatusCliParser to StatusCliArgumentParser for coherency. Define the no prompting options in ToolConstants. git-svn-id: https://svn.forgerock.org/opendj/trunk@2840 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
2. removed python unused Matcher class 3. fix for testcase identification to start dumping the STAX log into test-log.xml 4. fix for indexes test cases (added -n to dsconfig) git-svn-id: https://svn.forgerock.org/opendj/trunk@2839 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
alternate repositories. The current implementation is still the default server-wide mechanism using the config/schematokens.dat file, but it will be possible to use this API to create alternate implementations (e.g., one for the JE backend that stores the tokens in the database). This provides the first part of the fix for issue #2158. git-svn-id: https://svn.forgerock.org/opendj/trunk@2838 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…are now timed down to the second. subsecond timing would have been too platform(C library actually) dependent in python\n3. adapted the XSL to report the number of known issues\n4. Still need to fix coverage % XSL template\n5. other minor XSL fixes\n6. added windows new line support in environment.xml git-svn-id: https://svn.forgerock.org/opendj/trunk@2837 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2836 41b1ffd8-f28e-4786-ab96-9950f0a78031
28 Aug, 2007
12 commits
-
1. replace getNewServerAdsProperties(getUserData()) with ServerDescriptor to: a. align with new ReplicationCliMain b. allow implementing publicKeyCertificate entry independent of CLI/GUI. 2. inline getRemoteServerProperties (single caller) git-svn-id: https://svn.forgerock.org/opendj/trunk@2835 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Instead of closing the environment, deleting the files, and re-opening the environment, we are keeping the environment open and just truncating the databases. This dramatically reduces the amount of memory required to run the unit tests, apparently as a result of a memory leak in the Berkeley DB JE when the environment is repeatedly opened and closed. Note that the latest release of Berkeley DB JE (3.2.44, which we aren't yet using) claims to have a fix for a similar problem (JE issue #15444 as described in http://forums.oracle.com/forums/thread.jspa?messageID=1782659) but testing with that JE version didn't appear to resolve the problem so it is likely that the issue still exists. However, while it was causing a significant problem in our test cases, it is unlikely to cause problems in production environments because the JE environment should not be repeatedly opened and closed in the same JVM instance. git-svn-id: https://svn.forgerock.org/opendj/trunk@2834 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ng TestNG on some machines. git-svn-id: https://svn.forgerock.org/opendj/trunk@2833 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Clean up duplicate code in Installer.updateADS in preparation for adding instance public-key certificate to properties. External behavior (e.g., registeredNewServerOnRemote) should be unchanged. Ran precommit tests and various setup hand tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@2832 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2831 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2830 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
There is a new backend representing the certificate trust store, which allows the setup code to query and populate the trust store over protocol. However, we are using blind trust until that piece of the setup code is ready. The encryption settings are currently global to the server instance in a new crypto manager config entry. Authentication will always be performed so the main setting is whether to use encryption or not. In the future (post 1.0) we will need to allow encryption to be configured on or off depending on which replication server we are connecting to but we need some discussion on the best way to specify that in configuration. git-svn-id: https://svn.forgerock.org/opendj/trunk@2829 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2828 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Update the function that created the Message to be displayed to return a String instead of a Message object. git-svn-id: https://svn.forgerock.org/opendj/trunk@2827 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2826 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2825 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
send e-mail messages whenever an account status notification is generated. The message can be sent to the end user impacted by the notification (based on an attribute in the user's entry) and/or a fixed set of recipients. The messages that will be generated are created from template files, which can include tokens that will be replced with things like: - The name of the notification type - The notification message - The DN of the target user's entry - Attribute values from the target user's entry - Values of account status notification properties, which may vary based on the type of notification This change also includes a fix for a problem that could allow password expiration warning messages to be sent to a client even if the bind was not successful. OpenDS Issue Number: 581 git-svn-id: https://svn.forgerock.org/opendj/trunk@2824 41b1ffd8-f28e-4786-ab96-9950f0a78031
27 Aug, 2007
15 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2823 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
2 - fix in runTestJob: removed copy of results.html in tmp folder 3 - fix in staf-installer.xml removed references to results.html only rely on my-report.html now 4 - attach my-report.html to the in place of results.html 5 - added knowIssue facility to allow to tag tests failing because of known issues 6 - updated the XSL style sheet to show known issue 7 - added testcase coloring based on status pass/fail/unknown/known 8 - added table of contents title row to make it easier for newcomers to read the report 9 - added known bugs calls in backends group 10- added known bugs calls in security group 11- added known bugs call in logging group 12- fix in utils for default windows environment variables git-svn-id: https://svn.forgerock.org/opendj/trunk@2822 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
Also, modified the dsconfigSet function so that two of its existing parameters are now optional instead of required. This was necessary for such cases as set-global-configuration-prop where no object may be specified. git-svn-id: https://svn.forgerock.org/opendj/trunk@2821 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- Implemented as virtual attributes - They are enabled by default - numSubordinates and hasSubordinates methods added to the backend API and implemented for all existing backends - JE implementation uses the id2children index to keep count of the number of subordinates for each entry. - The behavior of exceeding the index-entry-limit (ALL-IDs) has changed to store a 8 byte entry ID set count with the most significant bit set to 1 instead of a 0 byte array to signify the index-entry-limit has been exceeded. The previous format is still compatible but all requests for numSubordinates will return undefined (-1). - The DBTest tool is also included in this fix. This can be used to list root containers, entry containers, database containers, index status, as well as dumping a database with or without decoding the data. Fix for issues 43 and 72 git-svn-id: https://svn.forgerock.org/opendj/trunk@2820 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2819 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Test case: 1. Create initial instance as stand-alone (no replication or ADS); 2. Create second instance as part of replication toplogy, specifying instance created in step 1. Configuration of instance 2 hangs in registering server with ADS. Works after this change; however, now get on OS X: $ ./setup Launching graphical setup... 2007-08-27 12:11:07.058 java[3932] CFLog (0): CFMessagePort: bootstrap_register(): failed 1103 (0x44f), port = 0x12503, name = 'java.ServiceProvider' See /usr/include/servers/bootstrap_defs.h for the error codes. 2007-08-27 12:11:07.061 java[3932] CFLog (99): CFMessagePortCreateLocal(): failed to name Mach port (java.ServiceProvider) git-svn-id: https://svn.forgerock.org/opendj/trunk@2818 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
rename "ds-cfg-ads-certificate" to "ds-cfg-public-key-certificate" use "ds-cfg-public-key-certificate;binary" git-svn-id: https://svn.forgerock.org/opendj/trunk@2817 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2816 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…t directly from Java core methods and replaced them with comments derived in most part from the parent methods git-svn-id: https://svn.forgerock.org/opendj/trunk@2815 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Cleanup around requesting instance public-key certificate from truststore backend. git-svn-id: https://svn.forgerock.org/opendj/trunk@2814 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2813 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2812 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
When debugging 2097 I've noticed that during a replication total update, if the updated server fails, the publisher thread on the other server hangs. The hang happens because normally the publisher thread never tries to reconnect after a protocol session failure but waits for the receiver threads to do the job but here the publishing activity is done in a receiver thread that holding the session lock and therefore prevent the other thread from doing there job. The solution is to move this work outside of the lock. I've tested this manually as it is difficult to automate. git-svn-id: https://svn.forgerock.org/opendj/trunk@2811 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The updates done to the task entry during an initialize task was sometime causing ConcurrentModificationException because they were done in an internal thread that can be in concurrence with the operation threads. The fix is to use the taskScheduler lock when updating the task entry git-svn-id: https://svn.forgerock.org/opendj/trunk@2810 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Update the code so that the log messages we received are written to the installer log file and also add some code to supress the output of certain operations in the progress dialog of the installer (in the case of the creation of the top entry). git-svn-id: https://svn.forgerock.org/opendj/trunk@2809 41b1ffd8-f28e-4786-ab96-9950f0a78031
26 Aug, 2007
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2808 41b1ffd8-f28e-4786-ab96-9950f0a78031
