Bugs Fixed in Directory Proxy Server

This section lists bugs fixed in Directory Proxy Server 6.1 and 6.0 releases.

Bugs Fixed in Directory Proxy Server 6.1

Following list contains only the selected bugs fixed in this release. For the complete list of the bugs fixed in this release, see the README.patchnumber file in your patch directory.

6445919

Directory Proxy Server cannot always resolve searches based on the virtual DNs.

6475156

The dpconf command erroneously claims a restart is required when you set some of the server's properties.

6475727

After using the dpconf delete-jdbc-object-class command, you must restart Directory Proxy Server for the change to take effect.

6475743

Directory Proxy Server has been seen to retrieve only one of two attributes mapped through JDBC with both attributes are mapped to the same database table column.

6479264

One level searches through JDBC data views have been seen to fail.

6486526

On Windows systems when you install Directory Proxy Server after Directory Server using the dsee_deploy command, the command returns an error suggesting that some common files could not be removed.

6492355

The JDBC database cannot handle the execution of partial LDAP transactions.

6494259

Directory Proxy Server does not recompute the alternate-search-base-dn property when you change the base-dn property of a data view.

6494400
6494405

On Windows systems when Directory Proxy Server is enabled as a service, do not use the dpadm cert-pwd-prompt=on command.

6494412

To enable email alerts from Directory Proxy Server to mail users on the local host, specify an email-alerts-message-from-address property before you enable email alerts.

6494513

Increasing the number of Directory Proxy Server worker threads can prevent the server from restarting. This problem manifests itself as a java.lang.OutOfMemoryError error when the server is started.

6500275

When used with the jvm-args flag to allocate extra memory for the Java virtual machine, the dpadm command has been seen to return exit status 0 even though memory allocation fails. Error messages appear on the command line, however.

6509148

By default, Directory Proxy Server disables SSLv2 as it is the oldest of the SSL/TLS family of security protocols and regarded as comparatively weak and obsolete. Now Directory Proxy Server enables only SSLv3 and TLSv1 security protocols.

6548377

LDAP response controls in searchResultDone dropped by Directory Proxy Server.

Bugs Fixed in Directory Proxy Server 6.0

4883696

Allow read and write requests to be chained separately.

4883701

Add alphabetic and hash based data distribution algorithms.

4951403

Directory Proxy Server cannot follow referrals in bind requests.

4975248

Directory Proxy Server log file cannot exceed 2 GB.

5014402

Directory Proxy Server file handles leak memory.

The following bugs were found during the beta program, and subsequently fixed.

6348105

Error arises when performing a search through Directory Proxy Server and password lockout occurs.

6445085

Directory Service Control Center does not allow you to create a certificate request.

6492361

LDAP searches through Directory Proxy Server are not abandoned by Directory Proxy Server after being abandoned by the client application.

6492368

Substring searches are not possible through a join data view.

6492371

Searching DB2 through Directory Proxy Server results in an SqlException.

6492375

When create a JDBC object class the secondary table is not optional.

6493640

Deleting an SQL database entry does not function properly.

6493643

Shared, multivalued attribute values in databases are ignored.