Exit Print View

Sun OpenDS Standard Edition 2.0 Release Notes

Get PDF Book Print View

Document Information

Installation Notes

What's New in Sun OpenDS Standard Edition 2.0?

Supported Operating Systems

Java Requirements

Supported Application Servers

Supported Locales

Software Environment Limitations and Recommendations

Related Documentation

Known Issues

Known Issues

This section lists the bugs that are known to exist at the time of the Sun OpenDS Standard Edition 2.0 release.

Note - The issue numbers in this section refer to issues logged in Issue Tracker. Numbers that begin with “CR...” refer to issues logged in BugTraq.


On OpenSolaris 2009.06, 64–bit, using the default JVM (1.6.0_13), the GUI setup and GUI uninstall do not work correctly. This is caused by a known issue in OpenSolaris 2009.06.

Rename or remove the $JAVA_HOME/jre/lib/accessibility.properties file and launch the setup or uninstall again.


If the directory server is running as a Windows Service, running stop-ds as a task does not stop the service.

Workaround: Run the stop-ds command locally, without scheduling it as a task.


On Windows systems, the output of non-ASCII characters is garbled in the French, Spanish, and German locales.

Workaround: Right-click on the title bar of the cmd.exe window and select Properties. On the Font tab, change the font to Lucida Console and click OK. In the cmd.exe window, run the following command:

C:\> chcp 1252

Some error messages are not translated. Errors with level SEVERE and FATAL are available in English only.


LDAP client connections record various monitoring statistics for total time and total requests. etimes are recorded in each LDAP connection handler monitor, using attributes of the form ds-mon-resident-time-operation-operations-total-time. Currently the etime-related statistics are calculated incorrectly and indicate the time spent queuing a request, rather than the time spent processing the request.

Note - etimes are recorded correctly in the access log.


On Windows systems, recurring backups do not work as expected. While the recurring task is created successfully, the backup fails with the following error:

An error occurred while attempting to back up backend backendName \
with the requested configuration

Non-recurring scheduled backups work as expected.


SASL encryption with a cipher strength of low does not work with a Java Runtime Environment (JRE) prior to version 1.6. With JRE 1.5, if a client requests a low cipher strength over a confidentiality quality of protection, the bind fails.

Workaround: Use JRE 1.6 or higher if you want to use a low cipher strength.


Setup fails when adding a server to an existing replicated topology and importing a large volume of data. Because the new server uses the default JVM options, attempting to initialize the server with a large volume of data fails with an out of memory error. There is no way to configure the JVM options during the setup.

Workaround: Set up the server in the topology, without initializing it with data, first. Configure the JVM options to be able to handle large volumes of data (see Configuring the JVM, Java Options, and Database Cache in Sun OpenDS Standard Edition 2.0 Installation Guide). Initialize the server with data by using dsreplication initialize (see Initializing a Replicated Server With Data in Sun OpenDS Standard Edition 2.0 Administration Guide).


On Windows systems no SNMP trap is sent if the server is stopped by using stop-ds with no credentials. The server is, however, stopped correctly. The SNMP trap is sent if the server is stopped by using stop-ds -D bindDN -p password.


The manage-account get-remaining-grace-login-count subcommand returns a value of one less than the actual number of remaining grace logins.


The output of the --help subcommand of all the command-line utilities is garbled in non-UTF-8 locales.


In rare cases, on particularly slow hardware, the default connection timeout of 10 seconds for some command-line tools is too short. This can result in these commands timing out before a connection has been established.


Running the ldif-diff command on LDIF files over a certain size (around 600 Kbytes on Windows systems, larger on UNIX systems) results in a memory error similar to the following: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space.

Workaround: Increase the heap size and rerun the command. For more information, see Configuring the JVM, Java Options, and Database Cache in Sun OpenDS Standard Edition 2.0 Installation Guide


In a replicated topology, if a server crashes directly after receiving delete operations, the delete operations might not be replicated to the other servers in the topology.

Workaround: The delete operations must be replayed manually on another server in the topology.

CR 6715991

There are links in the QuickSetup that point to the open source version of the documentation instead of to the corresponding Sun-supported documentation on docs.sun.com.

Workaround: Manually navigate to the Sun-supported documentation at http://docs.sun.com/coll/2508.1.