This section lists the bugs fixed in Directory Proxy Server 6.3.1 update 1.
Directory Proxy Server constructs illegal database requests.
Setting connectionIdleTimeOutInSec for LDAP listener can disable DSCC.
A search operation can return entries that contain attributes that are not present in viewable-attr.
The max-client-connections property is not enforced if no operation is performed on the connection.
Memory monitoring is disabled by default.
The numeric distribution algorithm should use long instead of int to set numeric bounds.
The Directory Proxy Server default size limit for resource properties uses the incorrect integer for unlimited.
DN transformations fail.
The setting of add-attr-value can cause DN transformations to produce incorrect output.
The bindDN should be mapped when binding to a LDAP server. (using DN mapping rule of the DV of the bindDN).
It is not possible to add a new virtual transformation with same "MODEL, ACTION, ATTR_NAME".
The requires-bind-password property set on a back-end directory server is not enforced.
Virtual DN mapping fails when depending on a virtual attribute.
Bind DN is rejected when transformation fails, even when it falls into the view.
Wrong DN mapping for the from server direction.
Upper/lowercase characters in attribute names are being transformed by 6.3 Directory Proxy Server.
A customer requested for Directory Proxy Server to set group permissions for config and log files (umask 117, chmod 660).
The dpadm start command dumps a core when using the MaxTenuringThreshold java argument.
DN mapping can drop renamed entries.
The dpadm does not generate a DPS.pid file.
Directory Proxy Server configuration schema are inconsistent with the SystemMonitorThread.java feature.
The server and console are inconsistent for searchMode parameter.
Directory Proxy Server fails when configured to use proxied authentication.
Allow for JAVA HOME to be set using dpadm set-flags.
DN mapping cannot be used on rootDSE.
Directory Proxy Server requires virtual DN transformation with multi-valued naming attributes.
Microseconds time granularity should be provided for etimes.
The splitldif command ignores virtual transformations.
Under heavy load, sockets can remain in the close wait state.
The SO_KEEPALIVE option is not set in Directory Proxy Server 6.3 (that is, setKeepAlive() != True) when a socket is created.
The fix for CR 6513526 can introduce regressions because of null values in ConfigAttribute objects.
The acceptBacklog property is ignored for channel-based listeners.
Inactivity heartbeats are not send often enough because of last activity on a backend connection.
Inactivity heartbeats are not sent for bound backend connections.
Backend server checks might not occur often enough because of last server activity.
The ldapsearch run on monitor entries can give inconsistent output.
An availability check should make sure that the backend server is down before cutting all connections.
A connection can become blocked in case of abandon request.
Better accuracy is required in the backend heart-beat.
A file descriptor leak occurs in server socket.
A null pointer exception can occur when searching on cn=monitor if a failover pool is defined with no source.
Directory Proxy Server continues opening connections to the directory server after an attempt to bind... fails.
Persistent search clients may not receive entry change notifications.
Two connections can share the same identifier.
Persistent searches are not cleaned up after client disconnect.
The proactive monitoring interval should be set to 1 second when a datasource is detected as down.
Directory Proxy Server associates different client operations with the same backend connection.
Backend connections are not closed but reused if idle is more than inactivity-timeout, causing a connection leak.
Connection pool housekeeping and health-check processing should be DEBUG.
Two simultaneous long binds assign the same backend connection to two clients connections.
Setting an incorrect jvm-path hangs the restart without any warning.
Directory Proxy Server returns the wrong error code when no back-end servers are available
An option should be provided to close client connection in case of "cannot retrieve backend connection".
Client affinity should not be enabled when useAffinity=false and affinityPolicy is explicitely set.
Directory Proxy Server cannot be started if one of the data source host is unreachable.
The dpconf command should support new attributes introduced in Directory Proxy Server 6.3.1_update 1.
The dpconf command should support bind DN mapping.
More simple versioning should be provided for management of Directory Proxy Server properties.
The dpconf should support monitorRetryCount.
Client affinity ignores the data source's read-only flag.
Implementation of fixes for CR 6714425 and 6714448 should be completed.
A lowercase join expression can cause SQL requests to fail.
Directory Proxy Server 6.3.1 performance is inadequate when more than 100 clients are performing persistent searches.
Persistent search thread looping and the Directory Proxy Server can no longer handle persistent searches
The performance of the persistent search is inadequate.
Creating 20 persistent searches and then stopping them causes persistent search functionality to fail.
Directory Proxy Server returns StringIndexOutOfBoundsException in certain cases of attribute mapping and virtual transformation.
The transformation and mapping rules do not perform as expected.
Threads can be released prematurely, producing an ASN.1 exception.
The Directory Proxy Server returns an incorrect error when the back end goes down.
An unexpected null pointer exception can be raised.
Under some circumstances, the password storage scheme can be ignored by the JDBC data view.
The Directory Proxy Server can return identical results when different users bind on a client connection.
Under some circumstances, the Directory Proxy Server can fail to start when using JDBC.
An unexpected ASN1 exception can occur and not be handled.