Hi Yeah removing the timeout handler is a good idea. And we love contributions, so feel free to log a JIRA and attach a patch. http://camel.apache.org/contributing.html
On Mon, Sep 2, 2013 at 10:05 PM, fbarbat <fbar...@gmail.com> wrote: > As a workaround, I implemented a handler which modifies the pipeline on every > request so the ReadTimeoutHandler is removed once the response is read. > Specifically, a CamelRequestTimeoutHandler is inserted before Camel's > ClientChannelHandler. My handler inserts a ReadTimeoutHandler on write and > removes it on read. > This has no problems with Camel use of Netty because of the pool of > channels. If the access to a single channel had been concurrent, this > workaround wouldn't have worked. I can send you a patch if you are > interested. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Netty-and-requestTimeout-tp5738341p5738536.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
