Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

LDAP Timeout after couple of hours


I've running a Jira and Bamboo instance, both on separate servers, same network. Both point to an Active Directory via LDAP, identical configuration.

AD contains roughly 20 Users and 20 Groups.

Jira works flawless and Bamboo gets some trouble after couple of hours. I can authenticate without a problem after startup for some hours, but then I start getting a timeout. Jira still works fine.

LDAP users fail to authenticate with response timeout errors in logs in Jira server | Jira | Atlassian Documentation

Not using follow refereal.

Restarting the Software, not the server, helps. Any ideas what causes the timeout? DCs are still reachable of course.

2 answers


I reviewed all settings and everything is correct.

But I started a tcpdump when the error happens and I can see...nothing. There is no outgoing connection.

However ping to DC, nslookup to DC and telnet on 389 to DC works fine.

0 votes
Brant Schroeder Community Leader Jul 08, 2021


If the users in Jira and Bamboo are the same I would suggest just setting Bamboo up to use Jira as its directory.  Then you have one directory to manage.

Since you have them set up separately I would suggest reviewing all the LDAP settings.  Pay particular attention to all your timeout settings and how often the sync occurs.  I have seen it when the sync occurs prior to the other completing eventually the thread gets stuck and everything begins timing out.  You should also check the logs and see if there are any specific LDAP errors.

Sry, I actually wanted to reply over here.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events