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.