Flooding listening port does

Question

Hello,
I have just been doing some perfomance testing on one of our applications . This application is running as a jboss service on CENTOS(linux) listening for requests on a particular port, whilst testing I discovered that if this service received too many connection request on one go it would accept the connection but would not return responses. It looks like the service just stops allocating ports after a specific number of connections. All ports seem to be recycled successfully, the only way I get it to return responses is by restarting the service. It works fine if I spawn say 10000 threads seperated by 50 milliseconds, it starts failing if the thread separation times is lower.
Here is my listener code:
           ServerSocket serverSocket = new ServerSocket(list_port);
            while (listening)
                System.out.println("Server waiting on port "+list_port);
                Socket clientSocket = null;
                clientSocket = serverSocket.accept();
                new SecureGprsServer(clientSocket).start();
                System.out.println("New request received");
            } From this code when its flodded it does not even print +"Server waiting on port "+list_port);+ I can even telnet to the port. Doing a netstat shows that all ports are killed gracefully.
Please help.

Answer 1

It looks like the service just stops allocating ports after a specific number of connections.But 'the service' doesn't 'allocate' any 'ports' relating to incoming 'connections'. Neither does Java. Neither does anybody else.
Are there any issues related to flooding socket listeners in java?No.
More probably you have run out of threads, or you have an undetected OutOfMemoryError, something like that.