[MGNLDAM-729] Reduce severity of random 'broken pipe' exceptions Created: 04/Sep/17  Updated: 11/Jan/18  Resolved: 11/Jan/18

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLDAM-679 Broken pipe when video is loaded Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Improve QA setup

 Description   

With MGNLDAM-679 we were able to make the errors triggered by video files that we'd get pretty consistently (both locally and on Jenkins) disappear.

However, builds on Jenkins still show the same exception from time to time:

[INFO] [talledLocalContainer] 2017-09-01 15:27:02,521 ERROR info.magnolia.dam.core.download.DamDownloadServlet: An IO error occurred during download
[INFO] [talledLocalContainer] org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:380)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:420)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:345)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:405)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:393)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:96)

As fgrilli ended up commenting, this could be due to a number of issues.



 Comments   
Comment by Antti Hietala [ 03/Nov/17 ]

Since it's only the tests we run on Jenkins builds where this error occurs, and it hasn't been reported by users, let's downgrade it from an error to a warning.

Comment by Antti Hietala [ 11/Jan/18 ]

Hasn't been happening lately.

Generated at Mon Feb 12 05:02:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.