Re: Socket limit?

On Mar 14, 2006, at 11:03, Rob Terrell wrote:

> I have a chat server that I wrote using  
> POE::Component::Server::TCP. It works great, except when it runs on  
> Windows (ActiveState Perl) there seems to be a limit to the number  
> of sockets that communicate. This is unrelated to the connection  
> limit added in POE .33.
> After 64 clients are connected and communicating, all additional  
> client connections seem to be accepted, but do not get serviced by  
> POE::Component::Server::TCP. When one of the existing connections  
> drops, then one of the "waiting" connections gets served.
> Does anyone know why this might be? SOMAXCON appears to be = 5,  
> which POE .33 doesn't seem to use anymore.
SOMAXCON defines the number of connections that can be waiting in the  
listen/accept queue before the system drops new connections.  It's  
not a limitation on the number of active connections you can have.
My guess is that either ActivePerl or Winsock has a descriptor limit  
in its select() implementation.  POE doesn't care, and it'll happily  
try to use more descriptors than your OS supports, if your  
application lets it.
--
Rocco Caputo - rcaputo@xxxxxxxxx