camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject [HEADS UP] - Jetty component and http clients
Date Sat, 15 Dec 2012 11:28:20 GMT

I have looked at:

The problem is that when using camel-jetty a jetty http client would
always be created, even if people only use the jetty consumer. This
leads to the jetty http client setup a thread pool with 8 live
threads, running for no good reason.

I looked at this, and discovered another issues that the http client
would be re-used by all jetty producers. This is not really the
intend, as each producer should have its own client by default. And
using a shared http client is only for special circumstances.
This is what we do in other http component with client support, eg
camel-http, camel-http4, camel-ahc etc.

So in this light I am deprecating some options in camel-jetty and
making sure camel-jetty creates a new http client for each producer.
This will fix CAMEL-5867.

For the 2.10 and 2.9 branches I would work on a minor fix to keep the
current options, by have them @deprecated.

Claus Ibsen
Red Hat, Inc.
FuseSource is now part of Red Hat
Twitter: davsclaus
Author of Camel in Action:

View raw message