Connection failed : javax.net.ssl.SSLException

Possibly fixed in r13590. Please update to the latest ​snapshot build available.

Reopened as problem still unresolved according to #7625.

Can you please try build 14077. It includes optimizations of r14071 and a possible fix in r14072 for partial lengths written with the multipart upload feature.

Hi As requested I downloaded the newest snapshop (14084) and attempted to upload my large files (250mb to 1.2gb in size) to S3.

Got the same error after approx 85mb of transfer (see screen grab).

Do you want me to turn on any logging/debugging?

Ivan

new error. click CONTINUE and it carries on for a short while.

At least for multipart uploads (triggered for uploads exceeding 100MB) you can resume the transfer to only upload missing parts.

Usually logging information will not give much clue to broken pipe failures which indicates a generic networking issue.

Is this specific to the SYD bucket or do uploads fail regardless of the location of the bucket?

Hi I have done some testing on different regional buckets (US standard, Oregon, Ireland) and they all fail with 10.6 workstation. I have connected via wire and wireless to remove local networking issues. Now trying on my old Win7 laptop with latest snapshot to see if its platform specific.

Also testing on 10.7 laptop to see if its anything to do with the java library issue between 10.6 and 10.7

All machines on different AWS keys just in case they are hitting some kind of login limit (which i doubt)

Any other thoughts?

Just finished testing. I get the same results from 10.7 and win7 (much less though). That makes me think network however testing with CrossFTP, 3Hub and Forklift there are no issues.

Hence it looks like a Cyberduck issue??

Any thoughts?

ps tried pressing CONTINUE when the error happens but thats like every few mins - the whole transfer is scheduled to take hours....

Replying to ivanhassan:

Just finished testing. I get the same results from 10.7 and win7 (much less though). That makes me think network however testing with CrossFTP, 3Hub and Forklift there are no issues.

Hence it looks like a Cyberduck issue??

Yes, that makes it hard to argue it is not an issue on our end.

Can you try to set the ​number of maximum transfers to 1 at the lower right corner in the Transfers window which as of build r14094 will limit the number of concurrent connections for multipart uploads to 1 as well.

transfer ok but hung on second job

Hi With r14094 the file transfered ok however the next job did not start - got stuck with Maximum connection exceeded.

I assume this looks like the multi-part upload issue which would explain the S3 disconnection (especially if they interpreted the multipart upload as DoS?)

Shall I try on 2 uploads?

Many thanks again

Ivan

Replying to ivanhassan:

Hi With r14094 the file transfered ok however the next job did not start - got stuck with Maximum connection exceeded.

I assume this looks like the multi-part upload issue which would explain the S3 disconnection (especially if they interpreted the multipart upload as DoS?)

Shall I try on 2 uploads?

Many thanks again

Ivan

With a slow connection and bad latency we were just congesting the line with 5 open connections per multipart transfer. With the change there is no parallelism for multipart uploads.

The Maximum connection exceeded is displayed on our part for transfers waiting for a slot.

So would you expect a 1Mb link to be able to support 2 transfers (ie 10 connections)?

Latency appears to be ok (33ms).

Could we build in an autochecker and if the line looks too congested, it reduces connections?

Just a thought...

Ivan

Replying to ivanhassan:

So would you expect a 1Mb link to be able to support 2 transfers (ie 10 connections)?

Latency appears to be ok (33ms).

Could we build in an autochecker and if the line looks too congested, it reduces connections?

Yes, we plan to do dynamic connection number adjustments based on failures and throughput.

#7625 closed as duplicate.

#6587 closed as duplicate.

#7424, #6801, #6587 closed as duplicates.

Fix in r14903 with Expect: 100-continue header for PUT requests that resolves broken pipe failures for uploads to buckets where a 307 Temporary Redirect is returned.