You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following some investigation from #398 led to the discovery that some directory listing operations also leak connections. Currently disentangling the BufferedReader close from the CloseableHttpResponse close to see where exactly this is occurring.
This seems to be more relevant to the parallelism of the findForkJoinPool when setting max_connections = 1 and is not actually a connection leak. Renamed.
The issue was in Mantaclient#listObjects intentionally returning an empty stream but forgetting to close the iterator used to determine the stream should be empty.
The text was updated successfully, but these errors were encountered:
tjcelaya
changed the title
MantaDirectoryListingIterator intermittently leaking connections
Revisit findForkJoinPool behavior when max_connections = 1
Jan 10, 2018
tjcelaya
changed the title
Revisit findForkJoinPool behavior when max_connections = 1
MantaClient#listObjects leaks a MantaDirectoryListingIterator when the iterator is empty
Jan 11, 2018
tjcelaya
added a commit
to tjcelaya/java-manta
that referenced
this issue
Jan 11, 2018
Following some investigation from #398 led to the discovery that some directory listing operations also leak connections. Currently disentangling theBufferedReader
close from theCloseableHttpResponse
close to see where exactly this is occurring.This seems to be more relevant to the parallelism of thefindForkJoinPool
when settingmax_connections = 1
and is not actually a connection leak. Renamed.The issue was in
Mantaclient#listObjects
intentionally returning an empty stream but forgetting to close the iterator used to determine the stream should be empty.The text was updated successfully, but these errors were encountered: