On Wed, Sep 28, 2011 at 4:17 AM, maccamlc <matthew.mcma...@ultra-avalon.com> wrote: > OK, when I use the option "disconnect=true" on the Client (NettyProducer) it > works, ie. does not stop routing after 10 messages. >
That sounds like it hit some default thread pool limits, which has 10 in the core pool size. Do you mind creating a simpler use case as an unit test, then we can use that to track down the issue? > But I don't understand why it is necessary to open a channel, write data, > get a response and then close the channel for every individual message. > > I feel that I must be missing something, with my usage of Camel and Netty. > > And advice is appreciated. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Netty-Producer-creating-new-connection-on-every-message-tp4844805p4847670.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
