[omniORB] omniNames crash with multiple connections

[Carsten Kraus]

Hello,

I am currently testing my server application by concurrently invoking
multiple instance of a program, simulating client activity. This client
program is fairly similar to the eg3_clt.cc example, only that it calls the
different server methods a few times instead of a single 'hello' call. 

Client and server seem to be working all right. I do have a little perl
script that repeatedly forks, and does a system call for executing the
client. Trouble starts after having forked off around 28 clients. Client 29
seems to crash omniNames (see below for a traceLevel 15 + trace invocations
output of omniNames). 

Thanks in advance for any suggestions,
  Carsten


connect from 10.0.6.9
omniORB: Initial reference `NameService' resolved from -ORBInitRef argument.
omniORB: tcpSocketMTfactory Rendezvouser: unblock from accept()
omniORB: tcpSocketMTfactory Rendezvouser: accept new strand.
omniORB: tcpSocketMTfactory Rendezvouser: block on accept()
omniORB: throw omniConnectionBroken from tcpSocketMTfactory.cc:1405
omniORB: tcpSocketMTfactory Rendezvouser: accept fails. Too many file
descriptors opened?
omniORB: tcpSocketMTfactory Worker: start.
connect from 10.0.6.9
omniORB: Handling a GIOP LOCATE_REQUEST.
omniORB: Dispatching remote call 'resolve' to: key<0x4e616d6553657276696365>
omniORB: Dispatching local call 'resolve' to root/<0>
libthread panic: cannot create new lwp : dumping core (PID: 26728 LWP 2)
stacktrace:
        fef027a4
        0