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.
