When a LDAP server that is not reachable from Artifactory either due to the change in the network or the LDAP server is unavailable causes threads to be accumulated.
Steps to reproduce:
1. Create a LDAP integration with Artifactory server and which is not reachable through the Artifactory instance
2. Try logging into the Artifactory instance through for or while loop with either internal or LDAP creds to simulate multiple requests to artifactory
3. We would see the Artifactory server will try to connect to the LDAP and get the following error message:
2020-07-20T16:44:40.944Z [jfrt ] [WARN ] [83974dcf00f21574] [LdapAuthenticationProvider:201] [tp-nio-8081-exec-982] - Failed to authenticate user: 'A' via LDAP: communication error
2020-07-20T16:44:50.952Z [jfrt ] [WARN ] [db16966acd2f7ae9] [LdapAuthenticationProvider:201] [tp-nio-8081-exec-984] - Failed to authenticate user: 'B' via LDAP: communication error
2020-07-20T16:45:00.953Z [jfrt ] [WARN ] [c6c976d9a60bfa97] [LdapAuthenticationProvider:201] [tp-nio-8081-exec-983] - Failed to authenticate user: 'C' via LDAP: communication error
Since the Artifactory is trying to make connections with the LDAP server and failing we would see the threads getting accumulated over the period of time and causing the Artifactory server unreachable.
The workaround is to disable the LDAP server or fix the network connectivity between the LDAP server and Artifactory