OpenDS 1.0 Release Candidate is now available.
By Ludo on Jun 13, 2008
The OpenDS development team is very pleased to announce the immediate availability of OpenDS 1.0.0-build016 which is the first (and hopefully last) Release Candidate for OpenDS 1.0.0.
We consider this release candidate complete, stable and suitable for testing by any user.
The purpose of the Release Candidate is to solicit one last round of testing before the final release.
So please test the OpenDS release with your client applications, in your environment or on your favorite platform.
If you do find a bug, please report it with Issue Tracker.
OpenDS 1.0.0-build016 is built from revision 4337 of our source tree, and has been uploaded to our promoted builds folder. The direct link to download the core server is: http://www.opends.org/promoted-builds/1.0.0-build016/OpenDS-1.0.0-build016.zip.
The direct link to download the DSML gateway is: http://www.opends.org/promoted-builds/1.0.0-build016/OpenDS-1.0.0-build016-DSML.war.
We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL http://www.opends.org/install/QuickSetup.jnlp, or visit https://www.opends.org/wiki/page/OverviewOfTheQuickSetupTool for more information.
OpenDS 1.0.0 is a pure Java, LDAPv3 compliant directory server, designed to provide high performance, to be highly extensible, and to be easy to deploy, manage and monitor. The final version of OpenDS 1.0.0 is expected to be released early July 2008.
Detailed information about the release candidate is available at http://www.opends.org/promoted-builds/1.0.0-build016
Major changes incorporated since OpenDS 1.0.0-build015 include :
- Revision 4231 (Issue #3236) — Fixed a null pointer exception that could be thrown when the server processed a modDN operation with a new superior entry that was in the subtree to be moved.
- Revision 4232 (Issue #3237) — Fixed the -Qand --nodetach options of the startds command on Windows platforms.
- Revision 4235 (Issues #3238 and #3240) — Fixed issues related to the start-ds and upgrade commands on Windows platforms.
- Revision 4237 — Updated the stop-ds error message to include connection information.
- Revision 4279 (Issue 3264) — Fixed workflow element creation ordering.
- Revision 4287 (Issue 3239) — Fixed jdmkrt.jar loading on Windows systems.
- Revision 4289 (Issue 2953) — Fixed the LDAPRequestHandler.
- Revision 4301 (Issue 3254) — Fixed an issue with the index counts if subtree deletes exceed the index entry count.
- Revision 4303 (Issues 3271, 3142, 3241, 3242, 3253) — Fixed various issues for the SNMP connection handler.
- Revision 4305 (Issue 3269) — Updated the example plug-in to allow users to add their own messages. The messages can be generated from a properties file.
- Revision 4308 (Issue 2911) — SynchronizationProvider API has been updated to properly listen for replication updates.
- Revision 4309 (Issue 3299) — Fixed an issue with the ACI group membership check.
- Revision 4311 (Issue 3261) — Fixed a post-external-initialization issue with dsreplicaton.
- Revision 4319 (Issue 3307) — Fixed a NullPointer exception when no certificate is defined for a registered entry in the ADS.
- Revision 4322 (Issue 3311) — Fixed import-ldif so that it creates a task when the --templateFile option and the --ldifFile option are specified.
- Revision 4326 (Issue 3272) — Fixed a connections issue at the end of QuickSetup.
- Revision 4327 (Issue 3295, 3304, 3306) — Fixed various SNMP issues.
- Revision 4327 (Issue 3266) — Added ds-cfg-max-allowed-client-connections parameter to prevent using up all file descriptors. By default, the directory server allows an unlimited number of connections as before, but the user can now adjust this to suit his system. The total number of client connections, DB files and log files must not exceed the max file descriptors limit from the OS (ulimit -n).
- Revision 4328 (Issue 3269) — Added checks for canceled operations in the JE back-end code.
- Revision 4333 (Issue 3318) — Fixed an issue with the status-panel code that logs the stack trace to a log file.