PDF Output Problem

Question

I have a servlet that takes a file from the server, reads its bytes with the FileInputStream, and writes them to the ServletOutputStream. The types we allow are pdf, tif, doc, and xls. The only problem I am coming across is some PDF files won't come up with the browser showing a 'File is damaged and could not be repaired' error dialog. The pdf itself seems fine. We can open it in Adobe Reader, and drag and drop it into the browser. It only seems to occur when running it through this servlet and only some PDFs, not all. I pasted relevant code below. It seems pretty basic to me.
Thanks,
Karl
out = response.getOutputStream();
file = new File(ApplicationData.getVar("DocumentPath")+attachedDoc.getPath());
response.setContentType(mimetype);
response.setHeader("Content-Disposition","inline");
// Get input stream for reading raw bytes
FileInputStream in = new FileInputStream(file);
byte[] bytes = new byte[10000];
// Read in file and at the same time write the stream to the resposne.
while((in.read(bytes)) != -1) {
     out.write(bytes);
in.close();
out.flush();
out.close();

Answer 1

Guess they are opting for something close to 8K
instead. Interesting.If by "they" you mean the reference in reply 7 above, the "they" is me. And my 8k value isn't very scientific. It's more like tradition from when disk blocks were usually 2k-8k. When accessing a disk, you may get improved performance when using disk block sizes or multiples thereof. For really kick a$$ performance (e.g. implementing a "cp" command), query the file system for its block size and use that unless the size is completely silly (statfs(2) system call in Unix gets the underlying block size).
When writing to a socket, the buffer size matters less. The Nagle algorithm will collect several writes to bigger packets, and the underlying network will require splitting up bigger writes.
Unless you are streaming lots of data over a gigabit net, your CPU will be able to keep the network card and the wire saturated at pretty much any buffer size. Maybe at less than, say, 100 bytes the CPU load will go measurably up. A couple of kB should be fine.