Re: ChannelInitializer.initChannel called multiple times

Actually, i am not sending any data over socket. i am just creating socket connection. On Wednesday, September 21, 2016 at 12:17:24 AM UTC+6, Rogan Dawes wrote: > > Firefox is closing the connection for some reason, and opening a newer one. > > Try logging the data transferred, to see what is ha

Re: ChannelInitializer.initChannel called multiple times

Firefox is closing the connection for some reason, and opening a newer one. Try logging the data transferred, to see what is happening. On Tue, 20 Sep 2016 at 8:04 PM john meyer wrote: > the thing is, it is trying for two connection but only a single connection > getting active so what can be re

Re: ChannelInitializer.initChannel called multiple times

the thing is, it is trying for two connection but only a single connection getting active so what can be reason of it ? On Tuesday, September 20, 2016 at 11:53:22 PM UTC+6, Norman Maurer wrote: > > Yeah this means that firefox opened two connections. So its expected to > run initChannel(….) two

Re: ChannelInitializer.initChannel called multiple times

Yeah this means that firefox opened two connections. So its expected to run initChannel(….) two times. One time per Channel (connection) > On 20 Sep 2016, at 10:45, john meyer wrote: > > > > On Tuesday, September 20, 2016 at 11:44:07 PM UTC+6, john meyer wrote: > @Norman > > Here is the log.

Re: ChannelInitializer.initChannel called multiple times

On Tuesday, September 20, 2016 at 11:44:07 PM UTC+6, john meyer wrote: > > @Norman > > Here is the log. when i am making a socket connection, it is trying to > create channel from two different port. > > Firefox: 48.0.2 > > > [id: 0xa64b3a8b, L:/xyz.422.190.204:5080 >

Re: ChannelInitializer.initChannel called multiple times

@Norman Here is the log. when i am making a socket connection, it is trying to create channel from two different port. Firefox: 48.0.2 [id: 0xa64b3a8b, L:/162.222.190.204:5080 - R:/119.30.38.248:41086] [id: 0xaf7922c3, L:/162.222.190.204:5080 - R:/119.30.38.248:41087] On Tuesday, September

Re: ChannelInitializer.initChannel called multiple times

Thanks norman Here is my pipeline @Override public void initChannel(SocketChannel ch) throws Exception { logger.info("=initChannel"+this); ChannelPipeline pipeline = ch.pipeline(); pipeline.addLast("codec-http", new HttpServerCodec()); pipeline.addLast("defla

Re: ChannelInitializer.initChannel called multiple times

Ensure its actually the same connection. I suspect firefox is opening two connections. > On 20 Sep 2016, at 09:30, john meyer wrote: > > I am getting a weird behavior in channel pipeline initializer. when a new > connection registered, initChannel() called two times. This is happening only >

Re: ChannelInitializer.initChannel called multiple times

Thanks Rogan, It is happening for both non-ssl and ssl. On Tuesday, September 20, 2016 at 10:44:13 PM UTC+6, Rogan Dawes wrote: > > Sound like odd behaviour with Firefox. > > Are you using ssl, perhaps? > > It might be that ff didn't like your certificate, and aborted, then > retried. > > Ro

Re: ChannelInitializer.initChannel called multiple times

Sound like odd behaviour with Firefox. Are you using ssl, perhaps? It might be that ff didn't like your certificate, and aborted, then retried. Rogan On Tue, 20 Sep 2016 at 6:30 PM john meyer wrote: > I am getting a weird behavior in channel pipeline initializer. when a new > connection regist

ChannelInitializer.initChannel called multiple times

I am getting a weird behavior in channel pipeline initializer. when a new connection registered, initChannel() called two times. This is happening only when i am testing client socket connection from firefox browser. Urgent help needed. what is the reason actually. Netty version: 4.1.5 -- Y