OpenDJ Fixes, Limitations, & Known Issues
This chapter covers the status of key issues and limitations
for OpenDJ ${docTargetVersion} and OpenDJ SDK ${sdkDocTargetVersion}.
For details and information on other issues,
see the OpenDJ issue tracker.
Key FixesThis release contains fixes that resolve security issues within OpenDJ.
Older versions of OpenDJ contain these security issues. It is recommended
that you upgrade to this release to resolve these security issues. ForgeRock
customers can contact support for details.
OpenDJ 2.6.0 and later maintenance releases
include important improvements to replication.
Replication remains fully compatible with earlier versions.
However, some operations that work fine with the current OpenDJ release,
such as replicating large groups
and replicating high volumes of adds and deletes,
can cause issues for earlier versions.
Make sure you upgrade all servers to this version
before allowing clients to take advantage of write operations
that could cause trouble for older servers.
The following important bugs were fixed in this release.OPENDJ-1322: Control-Panel.bat can not start and stop the OpenDJ server when running as a windows serviceOPENDJ-1283: Replayed Modify operations are rejected if the backend writability mode is internal-onlyOPENDJ-1275: Connections stop getting closed due to idle time outsOPENDJ-1270: Avoid unnecessary DNS lookups when performing bind requestsOPENDJ-1269: JMX connection counter not being decremented when connections are closed.OPENDJ-1266: State index is not updated when an index is deletedOPENDJ-1249: ConnectionFactory timeout setting is applied for Active Directory persistent search requestsOPENDJ-1247: Client side timeouts do not cancel bind or startTLS requests properlyOPENDJ-1228: Concatenated schema may contain more than valid schema, possibly leading to further issuesOPENDJ-1226: Upgrade should only consider .ldif files under config/schemaOPENDJ-1204: Access Log timestamp doesn't have milliseconds for Connect and Disconnect entriesOPENDJ-1200: SDK should use octet string matching by default for unrecognized attribute typesOPENDJ-1196: updateSchemaFile "succeeds" if it can't find schema in the templatesOPENDJ-1190: Under rare circumstances the DS replication recovery thread (RSUpdater) can spinOPENDJ-1183: Can not reset userPassword through REST interface due to lack of privilegesOPENDJ-1168: Warning message displayed when heartbeat check fails with a bind connection poolOPENDJ-1160: Write operations to non-groups force groups to be reloadedOPENDJ-1115: Internal errors from ModifyOperation - change number was not found in pending listOPENDJ-1090: ECL changenumbers get reset after a purge and server restartOPENDJ-1048: OpenDJ QuickSetup creates the "licenseAccepted" file in the wrong placeOPENDJ-877: ldifsearch.bat is not workingOPENDJ-661: TimeoutChecker throws NullPointerException on application shutdownLimitationsRelease has the following limitations,
none of which are new since .OpenDJ directory server provides full LDAP v3 support, except for
alias dereferencing, and limited support for LDAPv2.When you configure account lockout as part of password policy,
OpenDJ locks an account after the specified number of consecutive
authentication failures. Account lockout is not transactional across a
replication topology, however. Global account lockout occurs as soon as
the authentication failure times have been replicated.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.OpenDJ plugin extensions must follow the guidelines set forth in
the README file delivered in
opendj/example-plugin.zip. When developing your
extension, aim to remain loosely coupled with any particular version of
OpenDJ. Libraries used must be installed in
opendj/lib/extensions/ (or bundle them in your
.jar). Keep your configuration separate from the server configuration.
Also, unless you are reusing standard schema definitions, keep your
schema definitions separate as well.This can affect how your extension works after upgrade. In
particular opendj-accountchange-handler-1.0.0 does
not work with OpenDJ 2.6.0 after upgrade (OPENDJ-991). See that issue for notes on how make that version
of the extension work with OpenDJ 2.6.0.Known IssuesWhen deploying for production, make sure that you follow the
installation instructions on allowing OpenDJ to use at least 64K (65536)
file descriptors, and on tuning the JVM appropriately.The following important issues remained open at the time this release
became available.OPENDJ-1309: First dsreplication enable could warn before replicating schemaOPENDJ-1294: ldappasswordmodify -D <DN> -w - fails without prompting password from stdinOPENDJ-1290: Nested backends handles hasSubordinates attribute incorrectlyOPENDJ-1213: LDIFReader should reject LDIF that contains trailing spaceOPENDJ-1169: Exception/error lost when logging ERR_LOOP_REPLAYING_OPERATIONOPENDJ-1158: rebuild-index leaves backend offline if a backup is runningOPENDJ-1151: OpenDJ unable to initialize the SSL context an doesn't startOPENDJ-1146: Memory leak on opendj 2.6.0OPENDJ-1138: searchrate throws java.lang.IndexOutOfBoundsExceptionOPENDJ-1131: Rest2LDAP fails to start with GlassFish3.1OPENDJ-1094: ECL virtual lastChangeNumber attribute can decrementOPENDJ-1087: OpenDJ Console: Validation checks missingOPENDJ-1056: secure listener should not be created if proper keying material is not available for some reasonOPENDJ-1051: Upgrade: add task to update lastChangeNumber/firstChangeNumber attributes definition when upgrading from 2.4.xOPENDJ-1043: Worker Thread was interrupted while waiting for new work while shutting down OPENDJ-1016: Control panel does not follow static group recommendation from documentationOPENDJ-1009: CryptoManagerTestCase:testStreamEncryptDecryptSuccess failsOPENDJ-1007: InstallHelper: endless loop, etc.OPENDJ-948: unauthorized disclosure of directory contentsOPENDJ-934: Changes to RS window-size property require a server restartOPENDJ-862: Strange ds-privilege-name behaviorOPENDJ-810: Non-atomic password state updatesOPENDJ-640: Text Query Against indexed telephoneNumber Attribute Very SlowOPENDJ-573: mustChangePassword function makes-up password change stateOPENDJ-557: Identical changes recorded in duplicate changelog recordsOPENDJ-527: rebuild-index --rebuildAll corrupts the indexes for certain data sets OPENDJ-518: Cannot log into the administrative control panel with FIPS-140 enabled in certain casesOPENDJ-514: OpenDJ SDK SASL integrity/confidentiality violates protocolOPENDJ-505: dsreplication enable fails when hostname contains an underscoreOPENDJ-431: Server side sort control only works on result sets of less than 100000 entriesOPENDJ-412: Blocked persistent searches may block all worker threadsOPENDJ-365: Potential deadlock in JE backend while performing a mix of update operationsOPENDJ-270: dsreplication disable takes a long timeOPENDJ-49: Replication replay does not take into consideration the server/backend's writability mode.