Once shutdownOutput() has been done, the connection will still need to be
fillInterested to seek the close from the other end, thus it's idle timeout
will still apply. So either the close will arrive from the other end, or
idletimeout happens and then you should just close the endpoint.
On Tue,
Thanks for the response Greg. After writing the response and calling
shutdownOutput(), how do I set a forceful close timeout?
Thanks,
Josh
On Thu, May 20, 2021 at 3:09 PM Greg Wilkins wrote:
> There is nothing preventing you accepting a connection and then
> immediately sending an error
There is nothing preventing you accepting a connection and then immediately
sending an error response assuming a request is coming, and half closing
the connection. You can then give it a Connection class that just consumes
any characters received up to a low limit or short timeout.
On Fri, 21
Hi,
I'm using Jetty with a custom Connection/ConnectionFactory.
I want to impose a connection limit and I don't want to abruptly close the
connection without providing an error to the client. Rather, I'd like to
send an error message and then close the connection. But I can't send the
error
