Details
-
Suggestion
-
Resolution: Fixed
-
None
-
None
-
None
Description
I've found some scary-looking exceptions when looking at Tardigrade logs.
2010-12-11 00:55:08,857 ERROR [http-8085-3] [ArtifactDownloadStrategy] Failed to read : /opt/dogfood/panda/home/artifacts/SANDBOX-STB/JOB1/build-00158/Elastic/bamboo-elastic-agent-2.7.3.zip ClientAbortException: java.net.SocketException: Broken pipe at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:358) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:325) at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:381) at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:370) at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:89)
Fortunately, it only meant that the user has canceled the artifact download. We should not log output exceptions as an error (and the stack trace is unnecessary of course).