In terms of the connection, the client sends a FIN but the server does not respond.
That puts it into CLOSE_WAIT until the worker has eventually started and completed the
request.
As far as the application can tell, the response writer is still open when it's
finally served, and doesn't throw when writing/flushing, so I cannot detect the
situation there.
Thanks,
James
-----Original Message-----
From: undertow-dev-bounces(a)lists.jboss.org <undertow-dev-bounces(a)lists.jboss.org> On
Behalf Of James Howe
Sent: 27 February 2020 21:48
To: undertow-dev(a)lists.jboss.org
Subject: [undertow-dev] Worker queue timeout
Under load, when the worker threads are saturated, new requests will be queued.
Is there a way to timeout these requests, so that it doesn't waste time serving them
later when the client has already given up?
I saw a reference to RequestLimitingHandler having a configurable timeout, but that
doesn't appear to be true.
I also don't want any limit to how many request that can be waiting, only how long
they can wait.
This doesn't seem to be a feature offered by any of the standard Java ExecutorService
implementations, but perhaps Undertow has added this (or an appropriate extension point
for this) somewhere?
Thanks
James
_______________________________________________
undertow-dev mailing list
undertow-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev