Affects Version/s: 13.5.2, 14.0.0
Environment:OpenAM 14.0.0-M13 Build 089887dedd (2017-January-17 11:17)
CTS fail-back does not work properly. Tested on CTS Active-Passive deployment. CTS1 is used as primary which handle all the session, CTS2 only replicate a sessions. If I turned off the CTS1, CTS2 take active role, what is correct, but if I turn on CTS1 again, CTS2 is still a active.
CTS fail-over is set: /Configure / Server Defaults / CTS / External Store Configuration / Connection String(s) = riso-centos7.test.forgerock.com:1389,riso-ubuntu14.test.forgerock.com:2389
1.) Observe both CTS (OpenDJ) access logs and login as demo
I used "tail -f ./access | grep -v SEARCH" (-v = all logs lines except SEARCH apperas, it is because primary CTS contains a lot off these logs)
As you can see CTS 2 logs contains "type=synchronization" on ADD REQ what means replication session, CTS1 does not contain it, because session was created using this CTS1 (Active CTS)
2.) Turn off CTS 1 (primary)
Fail-over to CTS 2, you can login, to see that no type=sync appears in CTS2 access logs, because CTS 2 become Active (primary), also access log contains a lot of SEARCH REQ/RES
3.) Turn on CTS 1 and login with user, clear cookies and login more times.
You can see that sessions are created randomly in CTSs (sometimes in CTS1, sometimes in CTS2)
Also the SEARCH requests are still appears on CTS2 after fail-back. See example of these requests
All sessions should be created on primary CTS1 and SEARCH REQ/RES should not be on secondary CTS after fail-back