Hi Gowtham,
My first thought with this issue is that tying the S3 download
directly to your servlet output stream, and thus your end-user's
download speed, could be a problem. S3 is fairly unforgiving about
slight read/write delays, so anything that causes the download to
pause for a couple of seconds will likely lead S3 to close down the
connection.
I'm not sure that's the cause of the timeouts in this case, but it is
likely to become a problem in general since any pause in your
end-user's file download will probably cause your server's S3 download
to also pause. That is, assuming the servlet's output stream has some
kind of write-ahead buffer that can be exceeded, which is likely.
Can you decouple the two downloads by downloading from S3 to a
temporary file on your server, then sending an input stream of that
temporary file to your end-user? The mechanics of doing this could get
complex if the user's download speed is faster than the speed from S3,
but I suspect you're going to have to do something like this.
Aside from that, I'd look into the buffer sizes of all the relevant
streams. One of these buffer sizes will likely correspond to roughly
the size where your downloads start failing.
James
> --
> You received this message because you are subscribed to the Google Groups "JetS3t Users" group.
> To post to this group, send email to
jets3t...@googlegroups.com.
> To unsubscribe from this group, send email to
jets3t-users...@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/jets3t-users?hl=en.
>