mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git

pgamba
14.02.2008 5a9daed73a810ffd4c4d9c21df19b5605f07089d
refs
author pgamba <pgamba@localhost>
Thursday, February 14, 2008 10:02 +0100
committer pgamba <pgamba@localhost>
Thursday, February 14, 2008 10:02 +0100
commit5a9daed73a810ffd4c4d9c21df19b5605f07089d
tree 5743577f02d4b2d48fc96305917fe1bd9db79ef7 tree | zip | gz
parent 04e870d40ff37a78f8c89c0a91c479545bc92d4f view | diff
No Issue associated. A replication server RS registers under cn=monitor one entry for each peer RS, and one entry for each LS remotely connected to the peer RS (Undirect LDAP server entry). When 
the remote RS has new LS connecting to it, or LS disconnecting from it, it notifies the other RSes .. that's fine.
But when the connection between our RS and the peer RS itself is broken, some entities remains under cn=monitor while they should be removed.

1 files modified
7 ■■■■■ changed files
opendj-sdk/opends/src/server/org/opends/server/replication/server/ServerHandler.java 7 ●●●●● diff | view | raw | blame | history