Home
Analytics
Broken pipe with image/servlet during PDF render
kevinroll
I have a rather complex report that makes a call to a servlet to fetch an image. Everything is OK when viewing the report as HTML, but when I do a PDF strange things start to happen. Within my image servlet I get an exception when trying to write to the response:
ClientAbortException: java.net.SocketException: Broken pipe
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:358)
at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)
at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309)
at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)
at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
at javax.imageio.stream.FileCacheImageOutputStream.close(FileCacheImageOutputStream.java:213)
at javax.imageio.ImageIO.write(ImageIO.java:1567)
at com.verani.web.backPage.PropertyMapServlet.doGet(PropertyMapServlet.java:206)
It looks like BIRT hits the URL of the servlet several times and eventually receives a satisfactory reponse. The report *is* produced, and the image looks normal, but the frequent errors concern me. My guess is that for some reason BIRT aborts the connection before the servlet is ready with the response, and this happens several times until it succeeds. Due to the complexity of this report I can't produce a ready test case. Does this sound familiar to anyone? Thanks in advance.
Find more posts tagged with
Comments
JasonW
Are you using the BIRT viewer?<br />
<br />
Take a look at this bug:<br />
<a class='bbc_url' href='
https://bugs.eclipse.org/bugs/show_bug.cgi?id=234624'>https://bugs.eclipse.org/bugs/show_bug.cgi?id=234624</a><br
/>
<br />
If this is not your issue please log a new bug.<br />
<br />
Jason
kevinroll
I am using BIRT 2.3.2 under Ubuntu. I am previewing the report from within the designer... if I do this in HTML format I get the BIRT viewer, and things work normally, but when I preview in PDF I see this issue. The bug referenced above seems similar to my experience... I have seen both the PermGen exceptions and the identical broken pipe problem, although my circumstances are a bit different than that reporter. I'll try to dig a bit deeper and decide if a separate bug report is warranted.