I have posted the sample code in my previous post could you please take a look. Also below are my observation for HttpResponseDecoder
1. In 4.0.19 HttpResponseDecoder extends HttpObjecDecoder and HttpObjectDecoder extends Replyaing Decoder but in 4.1.1 HttpObjecDecoder extends ByteToMessageDecoder. 2. There are some code differences between 4.0.19 and 4.1.1 for HttpResponseDecoder. would the above changes causing this issue? On Thursday, June 30, 2016 at 9:49:29 AM UTC+5:30, Norman Maurer wrote: > > Can you share some code? > > Also can you share the code that setup the pipeline? > > Am 30.06.2016 um 05:33 schrieb Mani Chaitanya <[email protected] > <javascript:>>: > > It does work till 4.0.19 but with latest releases from 4.0.20 to 4.1.1 it > does not work for us. > Also I forgot to mention that we have used maxChunkSize of 131072 for > HttpResponseDecoder. > > On Wednesday, June 29, 2016 at 10:34:05 PM UTC+5:30, Norman Maurer wrote: >> >> Nothing I`m aware of… does it work with latest 4.0.x release ? >> >> >> On 29 Jun 2016, at 18:50, Mani Chaitanya <[email protected]> wrote: >> >> When I upgraded the libraries from 4.0.19 to 4.1.1 version suddenly our >> tunnel client stopped working. We have a tunnel client which talks to the >> tunnel server (sends messages in chunked format) using netty channels with >> 4.0.19 libraries everything is working properly i.e when we send a request >> message from tunnel client to the tunnel server, server sends response >> which we print the number of bytes i.e 1000 bytes in our tunnel client but >> with 4.1.1 in our tunnel client it prints two 500 bytes messages. Nothing >> has changed on the tunnel server side. >> >> The channelInbound handler used on the tunnel client when it receives the >> response from tunnel server will run in the below mentioned order >> >> 1. SslHandler >> 2. HttpResponseDecoder >> 3. HttpResponseLogger --> Here is the place where we print the number of >> bytes received. >> >> Is there any changes happened in 4.1.1 which is causing this? Any help is >> pretty much appreciated. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Netty discussions" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/netty/cc11ad1a-6cfd-4bab-a19e-ac439e6415ad%40googlegroups.com >> >> <https://groups.google.com/d/msgid/netty/cc11ad1a-6cfd-4bab-a19e-ac439e6415ad%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Netty discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/netty/b3ef9255-07de-4445-a258-55a153aa0fc5%40googlegroups.com > > <https://groups.google.com/d/msgid/netty/b3ef9255-07de-4445-a258-55a153aa0fc5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/4a13c805-0b0a-4120-9b96-de4902578e38%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
