camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tkopczynski <>
Subject [GitHub] camel pull request #1157: CAMEL-10240: Fix for thread pool sizes in CamelHtt...
Date Mon, 05 Sep 2016 19:07:22 GMT
GitHub user tkopczynski opened a pull request:

    CAMEL-10240: Fix for thread pool sizes in CamelHttpClient

    Fixes CAMEL-10240.
    Things I did:
    - Removed setting the `QueuedThreadPool` size to 16 in `CamelHttpClient`. Now it relies
on defaults in `QueuedThreadPool` class itself.
    - Added a constructor in `CamelHttpClient` for setting `HttpClientTransport`.
    - If the `httpClientMaxThreads` parameter is set, it becomes the selectors number for
the `HttpClientTransport` instance. I'm not sure about this one but I thought it might be
good to enable the possibility to configure this instead of having the dependency on `Runtime.getRuntime().availableProcessors()`
for all cases. But maybe it would be better to create a new parameter for this?

You can merge this pull request into a Git repository by running:

    $ git pull camel-10240

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1157
commit 6f12d971fe55738ee6f1e96b33917cd230d8af99
Author: Tomasz Kopczynski <>
Date:   2016-09-05T18:55:04Z

    CAMEL-10240: Fix for thread pool sizes in CamelHttpClient


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message