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

RE: How do I determine/change maximum number of concurrent connec tions (v. 2.0.7) under NT4/Win2K?

Actually, I'm not running it on NT server at all.  It's just a regular Win2K

Also, I find that even though the server hangs after the first test run,
when I abort my client application and run it again, this time the server
reports an error.  It seems the server hangs only during the first run,
which is pretty strange.  Running the server with full debug and log output,
I get the following (at the end of log output):

daemon: activity on 1 descriptors
daemon: new connection on 956
connection_init(956): connection table full (64/64)
daemon: connection_init(956, IP=, IP= failed.
daemon: closing 956
daemon: activity on: 124r
daemon: select: listen=124 active_threads=0 tvp=NULL

It seems that "connection table" only allows a maximum of 64 connections?
How is this determined, and more importantly, how can I increase this


-----Original Message-----
From: Kevin J. McCarthy [mailto:kevin@kogz.com]
Sent: Tuesday, September 04, 2001 8:44 PM
To: Boris Shpungin; OpenLDAP-software@OpenLDAP.org
Subject: RE: How do I determine/change maximum number of concurrent
connections (v. 2.0.7) under NT4/Win2K?

It may be a licensing issue with NT server. Are you using "per client"
or "per seat" licensing?

Are there Event Logs?


-----Original Message-----
From: Boris Shpungin [mailto:bshpungin@d2k.com]
Sent: Tuesday, September 04, 2001 10:07 PM
To: 'OpenLDAP-software@OpenLDAP.org'
Subject: How do I determine/change maximum number of concurrent
connections (v. 2.0.7) under NT4/Win2K?

To start, Hi everyone (it's my first post).  And thanks in advance for

I'm using the NT port of OpenLDAP 2.0.7 from FiveSight
(http://www.fivesight.com/downloads/openldap.asp).  I'm noping someone
on the list uses that build as well...  Also, I'm not on 2.0.11 due to
practices in our company -- but if you think that upgrading should
my problems, I'm all ears.

I have a simple Java test client that connects to OpenLDAP, using
Directory SDK.  For some reason, the NT build of OpenLDAP hangs after
approximately 60 connections have been opened up (without being closed).
Testing against OpenLDAP on Linux (Redhat 7.1), the same Java client
running from my Win2K machine) can make over 1000 connections, after
it doesn't hang but quits with an error.  Under Linux, it is obvious
the open descriptor limit is kicking in.  But what's happening under NT?
find it difficult to believe that NT limits open descriptors per process
something as ridiculous as 60.  On the other hand, why does the server
rather than reporting an error?

If anyone here has used OpenLDAP on NT or Win2K before, did you ever
problems such as this?  Any ideas as to possible cause(s) and solutions?

Many thanks.