Andrew O'Hara
10/25/2022, 6:14 PM4.33.1.0
version? It doesn't seem to actually break anything, but the volume of error logs are a problem.
UT005013: An IOException occurred
java.io.IOException: UT000034: Stream is closed
at io.undertow.channels.DetachableStreamSourceChannel.getOption(DetachableStreamSourceChannel.java:200)
at io.undertow.io.UndertowInputStream.<init>(UndertowInputStream.java:71)
at io.undertow.server.HttpServerExchange$DefaultBlockingHttpExchange.getInputStream(HttpServerExchange.java:2001)
at io.undertow.server.HttpServerExchange.getInputStream(HttpServerExchange.java:1615)
at org.http4k.server.Http4kUndertowHttpHandler.asRequest(Http4kUndertowHttpHandler.kt:34)
at org.http4k.server.Http4kUndertowHttpHandler.handleRequest(Http4kUndertowHttpHandler.kt:37)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:391)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:859)
at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2513)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1538)
at org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1282)
at java.base/java.lang.Thread.run(Thread.java:833)
dave
10/25/2022, 6:22 PMAndrew O'Hara
10/25/2022, 7:08 PM4.33.0.0
, and it's not always reproducible; maybe windows versus linux, or amd64 versus arm64, who knows.
And forcing undertow back did fix the issue. I think for now I'll just switch to the Jetty backend, but I'll be on the lookout for more reproducible scenarios in the future.