Replies: 1 comment
-
Could this be because And why would closing an inputStream properly on one side (downloading), affect the other side - uploading? |
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
-
I've recently refactored code that reads a gzipped S3 file,
From this:
To this:
Note that
privateObjMapper
is a JacksonObjectMapper
which is configured with.disable(JsonParser.Feature.AUTO_CLOSE_SOURCE)
, because thetry-with-resources
is supposed to callclose()
on all open resources.Elsewhere in the code, I have the following that UPLOADS S3 files:
This code is now continually getting the following exception (fuller traceback attached at end of post):
java.net.SocketException: Connection or outbound has closed
.The files ARE getting uploaded. So what's the significance of this exception and how can I avoid it?
Why is this happening? I've also tried calling
close()
on thes3Object
explicitly, but that didn't help either. Why was this message not displayed before, and is suddenly appearing? what am I missing?Traceback:
Beta Was this translation helpful? Give feedback.
All reactions