Confluence responds extremely slowly if LDAP connection times out

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 2.8
    • Affects Version/s: 2.2.9, 2.2.10
    • Component/s: None
    • Environment:

      LDAP configured

      Confluence takes several minutes to render pages when an LDAP connection is set as the primary user repository but the LDAP connection is timing out.

      Repository lookups that are expected to take a short time, such as group permission checks, should have a shorter timeout such as 5 seconds. Only when searching for users or groups should a long timeout be used.

      If the timeout is reached when attempting to login, the user should be informed that they should contact their administrator along with some technical information on the repository that timed out.

      To duplicate, Configure an LDAP server as per http://confluence.atlassian.com/x/sZAC Once the LDAP is fully configured, login as a local user, and force connection attempts to time out by choosing another IP, turning off the LDAP server, etc for the LDAP server

      1 - When a lookup to a repository is performed and times out, an error should be displayed in the browser.

      Report to to user on login page when a repository times out

      "An error occured - please contact your system administrator and inform them that "A user repository has failed due to timeout"

        1. atlassian-confluence-snippet.log
          19 kB
          David Soul [Atlassian]

              Assignee:
              Matt Ryall
              Reporter:
              David Soul [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: