in LDAP connection

Still need help?

The Atlassian Community is here for you.

Ask the community


There could be several symptoms to this problem : 

  1. JIRA is not able to connect to LDAP, or
  2. Users are not able to login, or
  3. Not able to add user directory.


The following appears in the atlassian-jira.log:

Caused by: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: ABC.PQR:389 [Root exception is No route to host]]


JIRA is not able to connect to the LDAP server because it is not able to resolve the path that it can use to the LDAP/Active Directory server.

There can be several reasons for this : 

  • There might be a reverse proxy in place that is blocking the connection
  • There might be a firewall in place between the servers that is blocking the port
  • JIRA server not being able to resolve the hostname of the LDAP server correctly, etc
  • There may be HTTP Access policies being pushed from ActiveDirectory, or puppet (preventing access to the LDAP Server)
  •  Overloaded domain controller, which caused JIRAs timeouts.

Having said this, this is a network issue instead of a JIRA issue.


  • Try the following steps to identify the problem :

    • ping ABC.PQR
    • telnet ABC.PQR 389
  • After the network issue is resolved, please login with a JIRA internal user
  • Delete the current LDAP connection

  • Set up a new one with the same credentials
  • Define a new, less loaded controller in configuration

Last modified on Sep 6, 2017

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.