A method 600 of managing a server having a dynamic number of processes that can change depending on the work load will now be described with reference to FIG. 6. The steps of the method 600 are the same as for the method 500 for steps 501 and 503-505. However, in response to receiving a TCP request 501, in step 602, the queue manager 133A increments a count of requests that have been received by the server 130. The queue manager 133A can store the count of requests that have been received in the local storage 136A, for example. Then, after the request is placed in the queue 504 or a rejection notification is sent 505, in step 606, the queue manager 133A increments a count of the number of rejections that the queue manager 133A has sent in response to TCP requests. The queue manager 133A can also store the count of rejections in local storage 136A, for example.

In step 607, the rejection rate is determined, for example, by dividing the count of the number of rejections by the total count of the requests that have been received by the server 130A. Alternatively, other techniques for comparing the number of rejections to the number of TCP requests (e.g., received total or within a given time period), or comparing the number of rejections to the number of TCP requests accepted (i.e., added to the queue 134A) can also be used. In one embodiment, the process manager 135A of the server 130A determines the rejection rate by pulling the relevant numbers from local storage 136A.