-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.0.0.2
-
Component/s: ldapjdk
-
Labels:
-
Environment:AM 6.0.0.2
-
Sprint:AM Sustaining Sprint 57, AM Sustaining Sprint 58, AM Sustaining Sprint 59
-
Story Points:5
-
Needs backport:No
-
Support Ticket IDs:
Bug description
When a LDAP server stops responding and a new connection is made there is an expectation that if the orignal server is brought back online, that this connection would be reestablished.
From what we are seeing when we reach the max pool size though we are not seeing any of the connections dropped to allow for the orignal server to start serving requests.
This cause a scenario where when a server goes down or becomes unresponsive it will end up with no load, and there is no automatic way to allow the Load to redistribute among the LDAP servers.
How to reproduce the issue
Details steps outlining how to recreate the issue (remove this text)
- AM configured to point to 3 LDAP servers behind a load balancer and a connection pool size for simplicity of 10.
- Start AM and have a balanced load of connections to LDAP servers
- Stop/disconnect LDAP server 1. This should cause LDAP 2 and 3 to now have all 10 connections
- Restart LDAP server1
Expected behaviour
When LDAP1 comes back online that it's orignal connections would be opened again so there would be a balanced number of connections
Current behaviour
LDAP2 and LDAP3 will continue to have all of the connections and no new connections will goto LDAP1 unless the a connection breaks or a server is marked as down.
- caused
-
OPENAM-15704 Suppress redundant log messages introduced via fix for OPENAM-14050.
-
- Open
-
- is duplicated by
-
OPENAM-13844 Configuration to force AM to drop connections to allow Load Balancer to Balance connections
-
- Resolved
-
- is related to
-
OPENAM-15679 The option "com.sun.am.ldap.connnection.idle.seconds" has a misspelling
-
- Resolved
-
-
OPENAM-15696 The attribute "com.sun.am.ldap.connnection.idle.seconds" with > 0 causes LDAP pool initialization failure when using external CTS / UMA
-
- Resolved
-
-
OPENAM-13844 Configuration to force AM to drop connections to allow Load Balancer to Balance connections
-
- Resolved
-
- is required by
-
OPENAM-14308 LDAP Connection Pool Minimum Size for Identity Store missing from XUI
-
- Resolved
-
- relates to
-
OPENAM-15620 Document the usage of "com.sun.am.ldap.connnection.idle.seconds"
-
- Resolved
-