Socket closed and null pointer exception when read/write to S3 #4388
Unanswered
espen-grodem
asked this question in
Migration from v1 to v2
Replies: 2 comments 2 replies
-
I went to the code to see what UrlConnectionHttpClient#getResponseCodeSafely is doing, and found this comment: @espen-grodem you wrote the error does not happen every time, how often does it happen? |
Beta Was this translation helpful? Give feedback.
2 replies
-
@espen-grodem I've also recently run into this with the exact same stack trace and SDK version (2.20.131) on corretto 1.8.0_422. Did you ever find a root cause or fix? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After upgrading to WS SDK for Java 2.x, we have occasionally gotten Socket closed exceptions when writing to S3. The error not on every write but quite often. Our client is defined as following
and the method for read and write to S3 as this:
To deal with the Socket closed exceptions I made the following changes to the S3 client:
This resultet in nullPointerExceptions occasionally when reading from S3.
Can anyone help me with this?
Stacktrace for both errors are pasted bellow
Stacktrace for Socket closed
Stacktrace for the nullPointer
Beta Was this translation helpful? Give feedback.
All reactions