Socket-Select problem

2009-06-10 Thread Anders Boström
Hello, I have a server that listens for messages on a socket. It works fine for some time but then it suddenly stops acting on messages from the connections! It creates a local socket with IO::Socket::INET and then a select object with IO::Select. In a loop it checks for connections with "->can_r

Hitting a maximum number of SOCKET connections?

2009-11-03 Thread Anders Boström
Hej, I have a server implemented in Perl. It handles multiple connection with the use of "IO::Select". All work well with the first 63 concurrent clients, but if client 64 and upwards sends messages, they will not be seen on the server as long as the other 63 client are connected to the server.

Re: Hitting a maximum number of SOCKET connections?

2009-11-03 Thread Anders Boström
Brian Raven skrev: > Anders Boström <> wrote: > >> ... >> All work well with the first 63 concurrent clients, but if client 64 >> and upwards sends messages, they will not be seen on the server as >> long as the other 63 client are connected to the s

Re: Hitting a maximum number of SOCKET connections?

2009-11-04 Thread Anders Boström
I have installed 5.10, but the problem still occures. The demo in http://www.mollehem.se/bilder/socketDemo.zip illustrates it. Any clue? Thanks Anders Brian Raven skrev: > Anders Boström <> wrote: > >> Hej, >> I have a server implemented in Perl. >> It handle

Hitting a maximum number of SOCKET connections? Continued...

2009-11-04 Thread Anders Boström
Hello again, I have received test result from 2 people that tested the example, and both failed in the same way. To clarify the previous explanation of the problem. Its seen on the server side! When the client has sent 63 PING's, the server stops showing the rest of the PING's (64-100). They wil