[omniORB] omninames: cannot create a worker fot this endpoint

[Duncan Grisby]

On Friday 13 October, Bruno Carlus wrote:

> I solved the "cannot create a worker fot this endpoint" problem with a
> thread pool but have now another problem:
> I've got about 1000 client app trying to fetch the reference of their
> server app. in tha name  service.
> When I  try to start  the server app,  he finds the name service but
> cannot bind its reference if there is more than 1009 (?)clients
> contacting the name service...is there some kind of limit there ?

There is no inherent limit in omniORB. The limit is either that the OS
has a hard limit on the number of file descriptors, or, more likely,
that you've hit the limit of the fd_set size. In thread pool mode,
omniORB uses select() to watch the incoming connections, so it can't
handle file descriptors outside the fd_set range. The solution to that
is to move to omniORB 4.1, which uses poll() instead of select(). poll()
has no limit on the file descriptor number.

The other thing that can help is to configure omniNames to close
connections more rapidly than default. Try setting scanGranularity to 1
and inConScanPeriod to 2.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --