S3AsyncClient putObject throwing status code 100 exception

[IvoMajic]

Describe the bug

When doing uploads to S3 as of recently I am getting the following exception:

software.amazon.awssdk.services.s3.model.S3Exception: null (Service: S3, Status Code: 100, Request ID: null, Extended Request ID: null)

The exception is not very informative as you see. Is there any way to debug this further? All was working correctly up until a few days ago.

Code example:

client.putObject(
PutObjectRequest.builder()
.bucket(properties.s3.bucketName)
.key(formKey(path, imageId))
.acl(if (isPublic) ObjectCannedACL.PUBLIC_READ else null)
.build(),
AsyncRequestBody.fromBytes(imageData)
)

The first response I get is:

HTTP/1.1 100 CONTINUE
Date: Sun, 02 Aug 2020 09:55:11 GMT
Connection: keep-alive

and then

HTTP/1.1 200 OK
Content-Length: 0
ETag: "d1aafcb9635d94434c4370260f956000"
Accept-Ranges: bytes
x-amz-request-id: tx0000000000000021ee840-005f268d7f-7c9455-default
Date: Sun, 02 Aug 2020 09:55:11 GMT
Connection: close that reached at the tail of the pipeline. Please check your pipeline configuration.

I am guessing it happens because the last 200 message is discarded, from the log:

2020-08-02T11:55:11,775 DEBUG [aws-java-sdk-NettyEventLoop-1-4] i.n.c.DefaultChannelPipeline: Discarded inbound message DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)

Seems to me it has something to do with Nettys handing of HTTP 100-Continue

Expected Behavior

The upload finishing successfully.

Your Environment

• Spring Boot 2.2.7
• AWS Java SDK version used: 2.13.65
• JDK version used: 1.8.0_262
• Operating System and version: Arch Linux

[debora-ito]

Hi @IvoMajic I was not able to reproduce the issue. My logs show HTTP/1.1 100 Continue

and then

HTTP/1.1 200 OK
x-amz-id-2: xxx
x-amz-request-id: xxx
Date: Thu, 06 Aug 2020 00:01:52 GMT
ETag: "xxx"
2020-08-05 17:01:52 [aws-java-sdk-NettyEventLoop-1-4] DEBUG software.amazon.awssdk.request:84 - Received successful response: 200

I wonder if this is caused by some network configuration. Are you using a proxy?
Can you provide the full stacktrace? Please make sure there is no sensitive data.

All was working correctly up until a few days ago.

Was there some other change that may have triggered the issue?

[github-actions]

It looks like this issue hasn’t been active in longer than a week. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please add a comment to prevent automatic closure, or if the issue is already closed please feel free to reopen it.

[danielGz]

@IvoMajic How did you fix it? I have the same problem, this 100 http status is pretty common, for multi part requests, Please re open the issue:
NettyNioAsyncHttpClient offers very little flexibility, if we could override or add additional channel pipelines in the netty client it could solve the problem. See https://stackoverflow.com/questions/63697436/spring-webflux-and-amazon-sdk-2-x-s3asyncclient-timeout for reference

[IvoMajic]

I also could not find a fix in the meantime. I agree this should be reopened, since it obviously is not a single instance.