You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2018/11/03 23:54:00 UTC
[jira] [Commented] (JCLOUDS-1465) Error with multipart upload to S3
for large files
[ https://issues.apache.org/jira/browse/JCLOUDS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674244#comment-16674244 ]
Andrew Gaul commented on JCLOUDS-1465:
--------------------------------------
Duplicate of JCLOUDS-1451?
> Error with multipart upload to S3 for large files
> -------------------------------------------------
>
> Key: JCLOUDS-1465
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1465
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 2.1.1
> Reporter: Blagoi Anastasov
> Priority: Major
>
> Hi,
> We have a problem with multipart upload to S3 for files above or even to 20GB. The exception is here:
> 2018-10-31 18:04:32,804 ERROR [EventQueueWorker-ThreadPool-16] s3.jclouds.ssl.CustomJavaUrlHttpCommandExecutorService - error after writing 24576/16800342 bytes to "some s3 container" java.io.IOException: Error writing request body to server at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3536) at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3519) at com.google.common.io.CountingOutputStream.write(CountingOutputStream.java:53) at com.google.common.io.ByteStreams.copy(ByteStreams.java:179) at org.jclouds.http.internal.JavaUrlHttpCommandExecutorService.writePayloadToConnection(JavaUrlHttpCommandExecutorService. java:298)
>
> We are using the last jclouds version (2.1.1). As we make transfers to S3 on a daily basis, the expected behavior is: files to be successfully uploaded. Now they fail while uploading the first part of the multipart file. I have examined similar issue: [http://mail-archives.apache.org/mod_mbox/jclouds-dev/201504.mbox/%3CCAHtp1K2vRaZxQCBAR8ZCjXoXxbnz58hNZCtFmmrNjYKSJ7dHgw@mail.gmail.com%3E] and it seems that it is not resolved. Have you identify it and start working on it? If not can you suggest any workaround?
> Best Regards,
> Blago
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)