[
https://issues.apache.org/jira/browse/JCLOUDS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076216#comment-14076216
]
ASF subversion and git services commented on JCLOUDS-624:
---------------------------------------------------------
Commit 793bb7609adbfb7a8bfb98257d28ed180dbea4ba in jclouds-chef's branch
refs/heads/master from Luciano P. Sabenca([email protected])
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-chef.git;h=793bb76 ]
JCLOUDS-624 - Fixed bug in ListNodes
To fix this bug, I used the approach debated in the above issue: create
new methods to do the operation using an ExecutorService provided by the
user.The the old methods are still working, but now the operations in
those methods are not concurrent anymore.
> Bug at ListNodes In ChefContext
> -------------------------------
>
> Key: JCLOUDS-624
> URL: https://issues.apache.org/jira/browse/JCLOUDS-624
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-chef
> Affects Versions: 1.7.3
> Reporter: Luciano Sabença
> Assignee: Ignasi Barrera
> Fix For: 1.8.0
>
>
> Hi.
> I've found a bug when using ListNodes in jclouds-chef. The problem is related
> to the thread pool that is used when ListNodes is called.
> When using ListNodes, for each node that exists in Chef, a new task is
> submitted to the pool "USER_THREADS". Each one of these submitted tasks
> generates another Runnable - to do the HTTP request - and submits it to the
> same thread pool. So, when we have a large number of nodes(an usual scenario
> when dealing with Chef), all threads in the pool are blocked waiting its own
> thread responsible to do the HTTP request and no thread is left to
> effectively do the HTTP request. After the configured timeout, a lot of
> java.util.concurrent.TimeoutException are thrown.
> I am already working to fix it and I will release a pull request soon (maybe,
> in a few days).
> Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)
