[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Openldap scalability problems

To: "Armbrust, Daniel C." <Armbrust.Daniel@mayo.edu>
Subject: Re: Openldap scalability problems
From: Howard Chu <hyc@symas.com>
Date: Tue, 31 Aug 2004 14:58:24 -0700
Cc: openldap-software@OpenLDAP.org
In-reply-to: <7A1D7964C7C943419AB6D2C32338385304642E0E@excsrv44.mayo.edu>
References: <7A1D7964C7C943419AB6D2C32338385304642E0E@excsrv44.mayo.edu>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040714

Armbrust, Daniel C. wrote:

p.s. - when it fails, the exception I get is:  javax.naming.TimeLimitExceededException: [LDAP: error code 3 - Timelimit Exceeded];
Normally, I would expect to see this if the search took longer than the value that I set in the SearchControls object. However, I am setting the timelimit to 0 on my searches, so I should never see this. OpenLDAP must be triggering this error when I hit the idletimeout value?

The idletimout only applies to idle connections. A connection with a running operation is (by definition) not idle. Some other parameter must be involved.

--
 -- Howard Chu
 Chief Architect, Symas Corp.       Director, Highland Sun
 http://www.symas.com               http://highlandsun.com/hyc
 Symas: Premier OpenSource Development and Support

References:
- RE: Openldap scalability problems
  - From: "Armbrust, Daniel C." <Armbrust.Daniel@mayo.edu>

Prev by Date: Re: allow bind_v2 not working?
Next by Date: RE: Openldap scalability problems
Index(es):
- Chronological
- Thread