OpenDJ Fixes, Limitations, and Known Issues OpenDJ issues are tracked at https://bugster.forgerock.org/jira/browse/OPENDJ. This chapter covers the status of key issues at release .
Fixes Since Last Release The following issues were fixed since release 2.4.2. TODO
Limitations Release has the following limitations. OpenDJ directory server provides full LDAP v3 support, except for alias dereferencing, and limited support for LDAPv2. Account lockout works on a per-server basis only. OpenDJ is not fully integrated with Microsoft Windows, yet OpenDJ directory server can be run as a service, and thus displayed in the Windows Services Control Panel. OpenDJ replication is designed to permit an unlimited number of replication servers in your topology. Project testing has, however, focused only on topologies of up to eight replication servers. On Niagara systems such as T2000, hardware SSL crypto acceleration runs more slowly than software crypto acceleration. To work around this issue take the following actions. Add more request handlers to LDAP (for TLS) and LDAPS (for SSL) connection handlers. Disable hardware acceleration for server's JVM by removing the SunPKCS11 security provider from jre/lib/security/java.security.
Known Issues The following known issues remained open at the time release became available. TODO Furthermore when deploying for production, make sure that you follow the installation instructions on allowing OpenDJ to use at least 64K (65536) file descriptors, tuning the JVM appropriately, and increasing database cache size from the default of 10%. For the latest status, query the OpenDJ bug database online at https://bugster.forgerock.org/jira/browse/OPENDJ.