[
https://issues.apache.org/jira/browse/JCLOUDS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated JCLOUDS-417:
--------------------------------
Description:
Users do not expect this behavior when aborting getBlob operations. Further,
by performing IO in finalize for un-closed JavaUrlHttpCommandExecutorServices,
the finalize queue may grow faster than the finalize thread can process. In
our system, this caused out-of-memory failures due to quick retry cycles.
was:
By performing IO in finalize for un-closed JavaUrlHttpCommandExecutorServices,
the finalize queue may grow faster than the finalize thread can process. In
our system, this caused out-of-memory failures due to quick retry cycles.
> Payload.getInput.close reads all bytes from its InputStream
> -----------------------------------------------------------
>
> Key: JCLOUDS-417
> URL: https://issues.apache.org/jira/browse/JCLOUDS-417
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
> Environment: Ubuntu 12.04
> Reporter: Thomas Manville
> Assignee: Thomas Manville
> Priority: Minor
>
> Users do not expect this behavior when aborting getBlob operations. Further,
> by performing IO in finalize for un-closed
> JavaUrlHttpCommandExecutorServices, the finalize queue may grow faster than
> the finalize thread can process. In our system, this caused out-of-memory
> failures due to quick retry cycles.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
