Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-users] Preventing queuing of requests when all connections exhausted

I want to configure Jetty client so that if all MaxConnectionsPerDestination are in use then additional requests to that destination immediately fail rather than queue. If a destination is hung, better to immediately fail over to another instance of the service than sit in the request queue for some multiple of the idle timeout.

Unfortunately, setting MaxRequestsQueuedPerDestination to zero prevents initiating any requests whatsoever. Setting it to the same value as MaxConnectionsPerDestination allows that many requests to be initiated, but once those requests are assigned to and consume connections a second batch of that many requests can be initiated and will queue waiting for the first batch to complete.

Any suggestions? If this required a new feature, what would the feature look like?

Back to the top