When the DJ LoadBalancer implementation is used with the following with a pre-binded authentication user, there seems to be failure cases that lead to continuous connection leak.
As a client OPENDJ sdk usage there seems to be issues trying to use the newFailoverLoadBalancer+newFailoverLoadBalancer+LdapClient.
When using the above with a wrong username/or password there is a background retry of these connections that causes leak
Run the attached testcase, but monitor the netstat or lsof to see that connection growth happens to DJ.
tested on DJ6. Tested on DJ6.5 (client libs) but no improvement
Use the attached testcase and monitoring the connection to DJ even after the connection is closed.
No connection leak
Connection growth leak even if there is no activity. The background checkIfAvailable in LoadBalancer is repeated get call and leaks connection regularly
If there is no wrong password or if no newFailoverLoadBalancer is used this issue is not seen.
Side concerns: It has been reported that this is one of the cases of leakage but there seems to be reported that even there is no issue with password, it is felt that if there is some exceptions, it is possible that connection leakage happens (so hopefully the solution here will also fix other related causes).