What steps will reproduce the problem?
1. Connect enough clients for one thread to have more than 64 connections
What is the expected output? What do you see instead?
I expect the server to keep handling clients until it reaches
maxThreads*maxSocketsPerThread.
Instead the server randomly picks a thread, and if that thread is full (64
connections) it just disconnects it.
What version of the product are you using? On what operating system?
1.0
Please provide any additional information below.
Original issue reported on code.google.com by Nay...@gmail.com on 29 Jan 2008 at 6:35
Original issue reported on code.google.com by
Nay...@gmail.com
on 29 Jan 2008 at 6:35