Same issue here with 4.1 docker base setup. To check the validity of Parameters and network status, I have created separate docker-openldap(refer:https://github.com/osixia/docker-openldap) server and tested Multi master replication where ldap search will be performed between docker containers(Add a new user "billy" on the first ldap server and Search on the second ldap server, and billy should show up!). But the same is not working with cache refresh setup as the test ldap server is always showing **Failed to connect to LDAP server**. Is it a bug or am I missing any thing here?
Below is the /opt/gluu/jetty/identity/logs/oxtrust_persistence.log
2020-05-14 18:43:50,243 INFO [qtp1818402158-14] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] (LdapConnectionProvider.java:234) - Attempting to create connection pool: 1
2020-05-14 18:44:36,863 INFO [qtp1818402158-10] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] (LdapConnectionProvider.java:234) - Attempting to create connection pool: 1
2020-05-14 18:45:35,246 ERROR [qtp1818402158-14] [gluu.persist.ldap.operation.impl.LdapConnectionProvider] (LdapConnectionProvider.java:83) - Failed to create connection pool with properties: {bindDN=cn=admin,dc=example,dc=org, useSSL=false, bindPassword=REDACTED, servers=ldap.example.org:389}
com.unboundid.ldap.sdk.LDAPException: An error occurred while attempting to connect to server ldap.example.org:389: IOException(LDAPException(resultCode=91 (connect error), errorMessage='Unable to establish a connection to server ldap.example.org/172.17.0.2:389 within the configured timeout of 100000 milliseconds.', ldapSDKVersion=4.0.14, revision=c0fb784eebf9d36a67c736d0428fb3577f2e25bb))
at com.unboundid.ldap.sdk.LDAPConnection.connect(LDAPConnection.java:875) ~[unboundid-ldapsdk-4.0.14.jar:4.0.14]