[
https://issues.apache.org/jira/browse/HTTPCORE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-162.
----------------------------------------
Resolution: Invalid
James
No wonder your application is running out of memory because it opens a new
connection for _each_ and _every_ URI it crawls while keeping all previous
connections alive.
Sam is absolutely right. This is exactly the case where a pooling connection
manager would make a lot of sense.
Again, please consider if NIO actually makes any sense for this particular
scenario. It is probably twice as slow compared to the classic BIO and is 10
times more complex.
Oleg
> Out of Memory when using ThrottlingHttpClientHandler
> -----------------------------------------------------
>
> Key: HTTPCORE-162
> URL: https://issues.apache.org/jira/browse/HTTPCORE-162
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 4.0-beta1
> Reporter: maomaode
> Attachments: 162-testcase.patch
>
>
> I'm hitting a Out Of Memory error when using ThrottlingHttpClientHandler
> <http://hc.apache.org/httpcomponents-core/httpcore-nio/apidocs/org/apache/http/nio/protocol/ThrottlingHttpClientHandler.html>
>
> with the Executors.newCachedThreadPool() , Will provide a testcase later
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
