Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Broken Pipe

    TomEE 8 / SmartGWT 12.1p

    We get the following on the server:

    java.io.IOException: Broken pipe
    at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
    at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
    at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
    at sun.nio.ch.IOUtil.write(IOUtil.java:65)
    at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
    at org.apache.tomcat.util.net.SecureNioChannel.flush(SecureNioChannel.java:124)
    at org.apache.tomcat.util.net.SecureNioChannel.close(SecureNioChannel.java:535)
    at org.apache.tomcat.util.net.SecureNioChannel.close(SecureNioChannel.java:559)
    at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doClose(NioEndpoint.java:1246)
    at org.apache.tomcat.util.net.SocketWrapperBase.close(SocketWrapperBase.java:422)
    at org.apache.tomcat.util.net.NioEndpoint$Poller.cancelledKey(NioEndpoint.java:770)
    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1735)
    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
    at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
    at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
    at java.lang.Thread.run(Thread.java:748)

    It happens when the browser client makes a GET call to https://myapp/sc/messaging?ts=1643654667993...

    The realtime messaging appears to still be working correctly, but is there a setting we can configure to avoid these errors?

    #2
    This basically means that the client has dropped the connection, which is ordinary and expected - it happens anytime the browser navigates away mid-request, or if the client cancels a request, and in various other circumstances.

    We are not in that stack - this is low-level IO stuff inside Tomcat - so we cannot squelch that message for you. You would need to look at the Tomcat docs and likely configure your logging system to not report this.

    Comment

    Working...
    X