That exception is logged at debug level, and basically happens when an
SSL connection is not closed cleanly. It can be safely ignored (in
general anything under io.undertow.request.io can be ignored, as it
basically means some kind of connection issue (such as the user
closing the browser window) that you can likely do nothing about).
In this case it is probably because if you use a self signed
certificate on the first connection the browser will abort the
connection, and display a warning/error page about the self signed
cert. Once you add the exception it should not happen again.
On Mon, Aug 8, 2016 at 7:20 AM, Edgar Espina <espina.edgar(a)gmail.com> wrote:
I'm playing with HTTP/2 and 1.4.0.Final and got a long stack trace on first
request, after first request no exception is generated or logged it.
You can reproduce this with a simple text response or with the HTTP/2
directory listing example.
Everything works as expected and exceptions are logged as debug not as
error... but I would like to know if this is expected or normal, as I said
everything works just got this ugly and log stack trace.
undertow-dev mailing list