That is nothing to worry about. It is actually a minor bug in the
message, it looks like you get the same message for both parse and
idle timeout. Either way it means the remote client has not sent any
data in a while, and Undertow is closing the connection as a result.
On Thu, Jan 19, 2017 at 7:53 AM, Miere Teixeira
I've changed the way my HttpHandlers are reading the body content (JSON) on
POST requests, reading them asynchronously as explained here.
Since then, my application log started to display messages like the
18:28:20.807 [XNIO-1 I/O-4] DEBUG io.undertow.request - UT005035: Closing
channel because of parse timeout for remote address /0:0:0:0:0:0:0:1:51781
Is it safe to ignore it? Is there something I should pay attention to use
undertow-dev mailing list