We are having general delays and socket timeouts when connecting JIRA to AD

[Pablo Venezia]

We have a JIRA development / test environment, whith same JIRA version that we have in production environment.

Production environment performance is ok, but dev / test environment is slow. 

We have recently overwritten dev database with production database.

User login is performed by connecting to a MS AD in both environments.

Hardware for both scenarios seem ok; JIRA shows enough free JAVA memory for both.

In dev env we are having general delays and specially socket timeouts when connecting JIRA to AD.

The connections from outside JIRA between servers look ok.

Have you had similar problems? How did you face them? 

Thanks.

Javier

[Brant Schroeder]

Javier,

  We have had similar issues when connecting to AD servers that are load balanced or round robin.  Turns out that this is something that Jira does not support.  You can read more about it here: https://confluence.atlassian.com/adminjiraserver073/user-management-limitations-and-recommendations-861253196.html

Here is a section from the link above:

Synchronizing with AD servers behind a load balancer is not supported. As with synchronizing between two different AD servers, Microsoft Active Directory does not replicate the uSNChanged attribute across instances. For that reason, we do not support connecting to different AD servers even when they are load balanced. You will need to select one server (preferably one that is local) to synchronize with instead of using the load balancer.

I would check this first and see if this is causing your issue.