How do I limit the number of connections Jetty will accept?

I have not deployed Jetty for my application. However used Jetty with some other opensource projects for deployment. Based on that experience: There are configuration for connector as below.

I have not deployed Jetty for my application. However used Jetty with some other opensource projects for deployment. Based on that experience: There are configuration for connector as below: acceptors : The number of thread dedicated to accepting incoming connections.

AcceptQueueSize : Number of connection requests that can be queued up before the operating system starts to send rejections. wiki.eclipse.org/Jetty/Howto/Configure_C... You need to add them to below block in your configuration 30000 20 8443.

The problem is, that the Acceptors just dump the connections on a queue as quickly as they can and then go and fetch more, so the OS limit is never reached. – airlust Apr 21 at 20:10.

AcceptQueueSize If I understand correctly, this is a lower level TCP setting, that controls the number of incoming connections that will be tracked when the server app does accept() at a slower rate than the rate if incoming connections. See the second argument to download.oracle.com/javase/6/docs/api/ja..., int) This is something entirely different from the number of requests queued in the Jetty QueuedThreadPool. The requests queued there are already fully connected, and are waiting for a thread to become available in the pool, after which their processing can start.

I have a similar problem. I have a CPU-bound servlet (almost no I/O or waiting, so async can't help). I can easily limit the maximum number of threads in the Jetty pool so that thread switching overhead is kept at bay.

I cannot however seem to be able to limit the length of the queued requests. This means that as the load grows, the response times grow respectively, which is not what I want. I want if all threads are busy and the number of queued requests reaches N, then to return 503 or some other error code for all further requests, instead of growing the queue forever.

I'm aware that I can limit the number of simultaneous requests to the jetty server by using a load balancer (e.g. Haproxy), but can it be done with Jetty alone? P.S.After writing this I discovered the Jetty DoS filter, and it seems it can be configured to reject incoming requests with 503 if a preconfigured concurrency level is exceeded :-).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.