Re: FetchS3Object leak

2017-03-22 Thread David Hesson
Hi James, Sorry - you are right. I searched for close and didn't notice it was in a try with resources block. The weirder thing is we only allow a single task to schedule at a time, which lead me to think it was leaking resources. I'll continue investigating and see if I can find out what's

Re: FetchS3Object leak

2017-03-22 Thread James Wing
David, Can you clarify which part of the FetchS3Object code looks problematic to you? From a quick look, I found one use of S3Object in FetchS3Object.java, line ~106: try (final S3Object s3Object = client.getObject(request)) { flowFile =

FetchS3Object leak

2017-03-22 Thread David Hesson
Greetings, In investigating a connection pool issue we were having during development, I was checking the FetchS3Object code to see how it reads content from S3. I don't see a close()