My Oracle Support Banner

DPS - Client Affiniity Policy Does Not Behave As Documented (Doc ID 1567054.1)

Last updated on MAY 17, 2018

Applies to:

Oracle Directory Server Enterprise Edition - Version 11.1.1.5.1 and later
Information in this document applies to any platform.

Symptoms

When using the client affinity policy 'read-affinity-after-write' we find that the DPS incorrectly sends all of a connected clients requests to the same DS after a write, rather than the 'first read request after a write request' as per the documentation. According to the DPS documentation ( http://docs.oracle.com/cd/E20295_01/html/821-1220/gbdhk.html#gbdhr ), with such a configuration only the first READ request is expected to go to the data source where the WRITE happened:

+++++++++++++++++++++++++++++++

read-affinity-after-write

    Affinity for the first read request after a write request

+++++++++++++++++++++++++++++++

But DPS is sending all READ requests to the data source where the WRITE was performed, and this was still happening even after the timeout expired.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.