Multiple worker thread is been spawned in camel-netty endpoint

["이희승 (Trustin Lee)"]

Hi Sachin,

Your question belongs to the Camel community because it's not us who wrote the camel-netty endpoint.

My guess is that camen-netty creates a new channel factory for each endpoint, where the expected behavior is to create only a single channel factory for all endpoints.

HTH

On Jul 26, 2011, at 9:34 PM, sachin2713 at gmail.com wrote:

> HI,
> 
> I am using Camel 2.6 with netty 3.2.3 for TCP communicaion.
> I am not using any route, just an tcp endpoint like below:
> <endpoint id="ByteStreamTransport" uri="netty:tcp://localhost:6123?   
> connectTimeout=5000&amp;sync=false&amp;decoders=#delimeter-
> decoder&amp;corePoolSize=1&amp;maxPoolSize=1"/>
> 
> Even though i have mentioned max pools size to 1, it's spawning new worker
> thread for every connection or request.
> 
> Please do explain differnce between handling a new connection and a new
> request to a port, i have gone through all the documention but not clear.
> what is the purpose of this max pool size here?
> 
> Regards
> Sachin
> 
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Multiple-worker-thread-is-been-spawned-in-camel-netty-endpoint-tp6622024p6622024.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users