Hi Willem, Thx for your input. I have fixed my problem by setting the parameter on the component itself
public void configure() throws Exception { NettyHttpConfiguration nettyConfig = new NettyHttpConfiguration(); nettyConfig.setMaximumPoolSize(2); NettyHttpComponent nettyHttp = new NettyHttpComponent(); nettyHttp.setConfiguration(nettyConfig); getContext().addComponent("netty4-http", nettyHttp); nettyHttp.start(); // expose a echo service from("netty4-http:http://localhost:{{port}}/echo") .log(">> Thread name : ${threadName}") .transform(body().append(body())).to("mock:result"); } Only 2 threads are created now Regards, Charles On Thu, Jan 14, 2016 at 2:33 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > Hi Charles, > > You should be able to setup the maximumPoolSize on the Netty4-http > component level due to CAMEL-8031[1]. > And the maximumPoolSize only works for consumer side. > > [1]https://issues.apache.org/jira/browse/CAMEL-8031 > > -- > Willem Jiang > > > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On January 14, 2016 at 1:09:04 AM, Charles Moulliard (ch0...@gmail.com) > wrote: > > Hi, > > > > When I debug this unit test > > https://gist.github.com/cmoulliard/123261f7ac2a9d5c719c, the Camel > Netty4 > > HTTP Endpoint is well created with the param "maximumPoolSize=2" > > > > main TRACE [org.apache.camel.impl.DefaultComponent] - Creating endpoint > > uri=[netty4-http://http://localhost:26025/echo?maximumPoolSize=2], > path=[ > > http://localhost:26025/echo], parameters=[{maximumPoolSize=2}] > > > > but the number of threads reported by Netty is still bigger than 2 > > > > Camel (camel-1) thread #4 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #4 - NettyEventExecutorGroup > > Camel (camel-1) thread #3 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #3 - NettyEventExecutorGroup > > Camel (camel-1) thread #2 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #2 - NettyEventExecutorGroup > > Camel (camel-1) thread #1 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #1 - NettyEventExecutorGroup > > Camel (camel-1) thread #0 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #0 - NettyEventExecutorGroup > > Camel (camel-1) thread #4 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #4 - NettyEventExecutorGroup > > Camel (camel-1) thread #3 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #3 - NettyEventExecutorGroup > > Camel (camel-1) thread #4 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #4 - NettyEventExecutorGroup > > Camel (camel-1) thread #0 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #0 - NettyEventExecutorGroup > > Camel (camel-1) thread #2 - NettyEventExecutorGroup INFO [route1] - >> > > Thread name : Camel (camel-1) thread #2 - NettyEventExecutorGroup > > > > Do I have to use another param to set the ThreadPool used by Netty4-http > ? > > > > > > Regards, > > > > -- > > Charles Moulliard > > Apache Committer & PMC / Architect @RedHat > > Twitter : @cmoulliard | Blog : http://cmoulliard.github.io > > > > -- Charles Moulliard Apache Committer & PMC / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io