[undertow-dev] Occurrence of write timeout on client\server side

[Stuart Douglas]

In order to see the effect of a write timeout you will need to attempt
to send a large response (e.g. 1mb), and have a client that does not
attempt to read from the socket (so the client sends the request,
keeps the connection open, but does not read the response).

Stuart

On Thu, Jul 27, 2017 at 9:58 PM, Вячеслав А <slavastap at gmail.com> wrote:
> Hello.
> I can't understand how "Write Timeout" works and when this timeout happens.
> I am using undertow as part of WildFly appserver.
> I can set Read Timeout as a small value (for example, 1 sec).
> And then all request will be rejected and browser request will be marked as
> closed (i can see this status in browser dev tools).
>
> But nothing happens when i set a small value for Write Timeout. All my
> request complete successfully.
> I am using also "clumsy" for slow speed emulation.
>
> I can see, that connection should be closed at break point:
> io.undertow.conduits.WriteTimeoutStreamSinkConduit.handleWriteTimeout
> I see, that "IoUtils.safeClose(this.connection)" called, but nothing happens
> in browser.
>
> Could you explain, please, how can i see the result of write timeout on
> server or client (prefered) side.
>
> _______________________________________________
> undertow-dev mailing list
> undertow-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/undertow-dev