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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,458,120
Community Members
 
Community Events
176
Community Groups

Where can I reconfigure the Timed call for search with handler timeout value?

Where can I reconfigure the Timed call for search with handler timeout value?

Our logs are filled with a huge number values that are between 1000ms-1150ms and we assume that's because this message is logged only when the duration goes above 1000ms.

```

2015-10-08 18:51:58,865 http-bio-8095-exec-958 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1073ms
2015-10-08 18:51:59,923 http-bio-8095-exec-958 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1057ms
2015-10-08 18:52:00,557 http-bio-8095-exec-849 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1069ms
2015-10-08 18:52:00,654 http-bio-8095-exec-912 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1078ms
2015-10-08 18:52:01,699 http-bio-8095-exec-844 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1432ms
2015-10-08 18:52:02,031 http-bio-8095-exec-912 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1369ms
2015-10-08 18:52:02,497 http-bio-8095-exec-755 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1372ms
2015-10-08 18:52:02,783 http-bio-8095-exec-844 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1083ms
2015-10-08 18:52:03,124 http-bio-8095-exec-912 INFO [crowd.directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on dc=citrite,dc=net took 1092ms

```

Also please note that this is the fastest DC from a forest of 38! The root cause is related to the way crowd queries are performed.

2 answers

0 votes

Hi, 


I am using JIRA Server 7.2.6, and I have an open LDAP directory.
I am using a similar issue.
My issue is that the directory auto syncs after 1 hour and it takes about 50 minutes to sync in total .
So basically it is syncing all the time. And the entires for syncronisation of the groups is always coming in the logs.

Did you find anything related to this?  How to increase the lookup time or how to stop the entries from popping in the logs? 

This, ignored, bug may be related to this issue https://jira.atlassian.com/browse/CWD-4179

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events