I guess you want to handle the ReadTimeout exception in your decoder. As we just add the ReadTimeoutHandler after the customer decoder and encoder, your decoder may not get the exception as you want.
The issue could be fixed by applying the ReadTimeoutHandler at the first place. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On January 14, 2015 at 8:57:06 PM, V4Vaithi (alagappan.i...@gmail.com) wrote: > ReadTimeout event is not triggered properly after adding custom > encoder/decoder to endpoint. > > I am using DelimiterBasedFrameDecoder & StringEncoder as custom codecs. > > My Route Confuiguration is as follows > > > > uri="bean:messageLogger?method=log" /> > > > uri="netty:tcp://127.0.0.21:2626?decoders=#stxEtxDecoder,#byteToString&encoders=#stxEtxEncoder&sync=true&requestTimeout=5000" > > > /> > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Netty-ReadTimeout-event-not-trigerred-tp5761676.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
