Revision 3154
Added by Chris Jones almost 18 years ago
| metacat.properties | ||
|---|---|---|
| 116 | 116 |
|
| 117 | 117 |
ldapbase=dc=ecoinformatics,dc=org |
| 118 | 118 |
|
| 119 |
# time in milliseconds allowed for ldap server connections |
|
| 120 |
ldapconnecttimelimit=5000 |
|
| 121 |
|
|
| 122 |
# time in milliseconds allowed for ldap server searches |
|
| 123 |
ldapsearchtimelimit=30000 |
|
| 124 |
|
|
| 125 |
# count of return entries allowed for ldap server searches |
|
| 126 |
ldapsearchcountlimit=30000 |
|
| 127 |
|
|
| 119 | 128 |
referral=follow |
| 120 | 129 |
|
| 121 | 130 |
#ldapurl=ldap://ldap.nceas.ucsb.edu:389/ |
Also available in: Unified diff
As part of a fix for http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2747,
I'm adding a few configuration parameters to metacat.properties:
1) ldapconnecttimelimit limits the time in milliseconds allowed for
LDAP server connections. This reduces the impact of any single
LDAP directory that may be unreachable (one of the referrals).
2) ldapsearchtimelimit limits the time in milliseconds allowed for
LDAP server searches. Again, servers with massive trees to search
might prove to be problematic, or servers that connect but do not
search correctly.
3) ldapsearchcountlimit limits the number of return entries allowed
for LDAP server searches. This is set pretty high (30000), but may
need to be altered when the KNB goes gold or platinum.