Troubleshooting Warnings in Log

0
Hello Gang... I was digging through log-messages, a good custom on a lazy Thursday-afternoon and ran into this one. AFAICT it does not show up in the GUI (and I did not get any Feedback from the client, but what am I looking at here? Blockquote Dec 10 16:27:47.409 127.0.0.1 tr10000: WARNING - Connector: Caught IOException while trying to write data to a client connection: null Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (1/74) org.eclipse.jetty.io.EofException: null Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (2/74) at org.eclipse.jetty.http.HttpGenerator.flushBuffer(HttpGenerator.java:914) Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (3/74) at org.eclipse.jetty.http.AbstractGenerator.blockForOutput(AbstractGenerator.java:523) Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (4/74) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:170) Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (5/74) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:107) Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (6/74) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1720) Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (7/74) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1696) Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (8/74) at org.apache.commons.io.IOUtils.copy(IOUtils.java:1671) Dec 10 16:27:47.411 127.0.0.1 tr10000: WARNING - Connector: (9/74) at com.mendix.webui.requesthandling.FileRequestHandler.sendDocument(FileRequestHandler.scala:377)
asked
2 answers
1

Do you have any idea what was happening when this warning popped? There is mention of sendDocument and IOUtils.copy. That in combination with an EoFException.. Sounds like there was an issue with copying contents to or from a document?

Just thinking out loud here :-)

answered
1

Lex are you sure you have included the complete message in your post?

My guess is that what happened here is that the server was sending a file to a client when the connection suddenly died. If that's indeed what happened it's something that's pretty normal.

answered