Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 16 Mar 2016 07:17:33 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12950597.1458061989000.32650.1458112653624@Atlassian.JIRA>
In-Reply-To: <JIRA.12950597.1458061989000@Atlassian.JIRA>
References: <JIRA.12950597.1458061989000@Atlassian.JIRA>
 <JIRA.12950597.1458061989532@arcas>
Subject: [jira] [Commented] (CAMEL-9713) Can not set custom Jetty HttpClient
 to producer endpoint
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-9713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196923#comment-15196923 ] 

Claus Ibsen commented on CAMEL-9713:
------------------------------------

Ah yeah the uri is rebuild for the producer to call with those non camel parameters, and therefore we need to remove the client also. Thanks Joe.

> Can not set custom Jetty HttpClient to producer endpoint
> --------------------------------------------------------
>
>                 Key: CAMEL-9713
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9713
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jetty
>    Affects Versions: 2.15.1
>            Reporter: Joe Luo
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.17.0
>
>         Attachments: camel-jetty-shared-client-patch.txt
>
>
> The camel-jetty page has a "httpClient" option that can be set on camel-jetty producer endpoint and it says:
> {code}
> To use a shared org.eclipse.jetty.client.HttpClient for all producers created by this endpoint. This option should only be used in special circumstances.
> This option should only be used in special circumstances.
> {code}
> In some cases, user might want to set a shard Jetty HttpClient among camel-jetty producer endpoints. For instance, user might use recipientList with camel-jetty producer endpoint to support multiple dynamically created URLs. So setting a shared Jetty HttpClient with a shared thread pool would be ideal to avoid exploding number of producer endpoints + their own producer thread pools in this use case. However, there is no way to set it to camel-jetty producer endpoint.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)