-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.60.3 LTS
Pipeline Stage View Plugin 2.9
When I click on my pipeline job and then on another link (i.e. the results link) before the pipeline stage view graphs are fully loaded, I see the stack trace below in the logs. We have a number of stages and builds on our pipeline job and it does occasionally take several seconds for the pipeline stage view information to fully display. Clicking on the build results number before the stage statistics fully loads will cause the error to appear in the logs.
Nov 04, 2017 2:33:41 AM hudson.init.impl.InstallUncaughtExceptionHandler$1 reportException WARNING: null org.eclipse.jetty.io.EofException at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:192) at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:408) at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:364) at org.eclipse.jetty.io.SelectChannelEndPoint.onSelected(SelectChannelEndPoint.java:111) at org.eclipse.jetty.io.SelectorManager$ManagedSelector.processKey(SelectorManager.java:640) at org.eclipse.jetty.io.SelectorManager$ManagedSelector.select(SelectorManager.java:611) at org.eclipse.jetty.io.SelectorManager$ManagedSelector.run(SelectorManager.java:549) at org.eclipse.jetty.util.thread.NonBlockingThread.run(NonBlockingThread.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: 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.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:170) ... 11 more
I can confirm that latest LTS is having the same issue: